Professional Documents
Culture Documents
ProteusAMT-L RevJ
ProteusAMT-L RevJ
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.
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.
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 Incorporated
4000 Greenbriar
Stafford, TX 77477
USA
Tel 281.263.6500
Fax 281.263.6400
Toll free in US 1.888.225.6429
Internet: www.microwavenetworks.com
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.
Table of Contents
Lists all chapters, sections, headings, and subheadings in the manual, as well
as where to find them.
Chapter 2–Installation
Instructions on how to unpack, configure, and install the radio.
Chapter 3–Commissioning
Instructions on how to align, configure, power, and test a radio and
microwave hop.
Chapter 4–Operation
Describes 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.
Table of Contents
Chapter 1 — Radio Description
Overview ....................................................................................................................... 1-1
System Components........................................................................................... 1-2
Fault Protection .................................................................................................. 1-2
Indoor Unit .................................................................................................................... 1-3
Chassis................................................................................................................ 1-3
IDU Circuit Boards ............................................................................................ 1-4
Front Panel ......................................................................................................... 1-5
Line Interface ..................................................................................................... 1-6
Radio Capacity Configuration........................................................................... 1-7
Outdoor Unit................................................................................................................ 1-10
Radio Frequency Unit ...................................................................................... 1-10
Antenna ............................................................................................................ 1-12
IDU-to-ODU Interface Cable ...................................................................................... 1-14
Radio Management...................................................................................................... 1-15
Element Manager ............................................................................................. 1-16
EM Connections ..................................................................................... 1-16
SNMP ............................................................................................................... 1-17
SNMP Connection .................................................................................. 1-17
Text-Based Menu Interface.............................................................................. 1-18
Text-Based Interface Connection ........................................................... 1-18
Telnet................................................................................................................ 1-18
Telnet Connection................................................................................... 1-19
In-Band NMS Mode ............................................................................... 1-19
System Specifications.................................................................................................. 1-20
General Radio Specifications ........................................................................... 1-20
System Performance: Power and Threshold .................................................... 1-22
Ethernet Performance: Throughput and Latency ............................................. 1-23
Chapter 2 — Installation
Installation Information ................................................................................................. 2-1
Location.............................................................................................................. 2-1
Environment ....................................................................................................... 2-1
Grounding........................................................................................................... 2-2
Cable and Connector Considerations ................................................................. 2-2
Tools and Material......................................................................................................... 2-3
Preparing the Site .......................................................................................................... 2-3
Mounting the Rack ............................................................................................. 2-3
Unpacking Equipment........................................................................................ 2-4
Installing the Coaxial Cable .......................................................................................... 2-5
Assembling the Cable......................................................................................... 2-5
Chapter 3 — Commissioning
Powering the Radio ....................................................................................................... 3-1
Verifying Radio Configuration ..................................................................................... 3-2
Aligning the ODU ......................................................................................................... 3-4
Course ODU Alignment..................................................................................... 3-4
Fine ODU Alignment ......................................................................................... 3-5
Alignment Procedure ................................................................................ 3-5
Making Configuration Changes .................................................................................... 3-7
Configuring the ODU......................................................................................... 3-7
Setting Transmit and Receive Frequency ................................................. 3-7
Setting Transmit Power Output ................................................................ 3-7
Configuring the IDU .......................................................................................... 3-8
Setting Capacity........................................................................................ 3-8
Setting Tributaries .................................................................................... 3-8
Setting NMS Mode ................................................................................... 3-9
Verifying Radio Operation .......................................................................................... 3-10
Chapter 4 — Operation
Introduction ................................................................................................................... 4-1
Basic Operation ............................................................................................................. 4-1
Indoor Unit (IDU).......................................................................................................... 4-2
Line Interface ..................................................................................................... 4-3
Signal Multiplexing............................................................................................ 4-3
Modulation and Coding...................................................................................... 4-5
IF Conversion and Multiplexing ........................................................................ 4-5
Chapter 5 — Maintenance
Introduction ................................................................................................................... 5-1
Customer Service Options............................................................................................. 5-1
Support Contacts ................................................................................................ 5-1
Repair and Exchange Services ........................................................................... 5-1
Technical Support Services................................................................................ 5-2
Maintenance .................................................................................................................. 5-3
Changing Payload Configuration ....................................................................... 5-3
Upgrading Payload Capacity and Data Type ..................................................... 5-5
Replacing IDU Fuses and the Backup Battery................................................... 5-6
Replace the Power Supply Fuse ............................................................... 5-6
Replace the Backup Battery...................................................................... 5-7
Replacing IDU Depot-Level Components ......................................................... 5-8
Replace the Power Supply Board ............................................................. 5-8
Replace the IF Board ................................................................................ 5-9
Replacing ODU RF Units ................................................................................ 5-10
Updating Firmware with TFTP ........................................................................ 5-11
Using EM to Update Firmware............................................................... 5-11
Using CTI to Update Firmware .............................................................. 5-12
Loading Firmware with Bootloader ................................................................. 5-13
Maintenance Checks.................................................................................................... 5-15
Periodic Maintenance....................................................................................... 5-15
Monthly Checks...................................................................................... 5-15
Semi-Annual Checks .............................................................................. 5-15
Annual Checks........................................................................................ 5-15
List of Tables
Chapter 1 — Radio Description
Table 1-A Early-Model IDU Part Numbers.......................................................................... 1-3
Table 1-B Current-Model IDU Part Numbers...................................................................... 1-3
Table 1-C IDU Boards ........................................................................................................ 1-4
Table 1-D IDU Front-Panel Features.................................................................................. 1-5
Table 1-E Radio Configurations ......................................................................................... 1-7
Table 1-F ETSI Radio Capacity and Payload Configurations............................................. 1-8
Table 1-G ANSI Radio Capacity and Payload Configurations............................................ 1-9
Table 1-H RF Unit Part Numbers...................................................................................... 1-11
Table 1-I RF Unit Connections ......................................................................................... 1-11
Table 1-J IDU-to-ODU Cable Components ...................................................................... 1-14
Table 1-K General Specifications ..................................................................................... 1-20
Table 1-L Environmental Specification ............................................................................. 1-21
Table 1-M Mechanical Specification ................................................................................. 1-21
Table 1-N Power Specification ......................................................................................... 1-21
Table 1-O RF Transmit Power.......................................................................................... 1-22
Table 1-P System Specifications – ETSI Bandwidths....................................................... 1-22
Table 1-Q System Specifications – ANSI Bandwidths...................................................... 1-22
Table 1-R Hot-Standby Branching Loss ........................................................................... 1-22
Table 1-S Ethernet Data Throughput & Latency, ETSI Bandwidths ................................. 1-23
Chapter 2 — Installation
Table 2-A Installation Kit..................................................................................................... 2-2
Table 2-B IDU-to-ODU Cable Components........................................................................ 2-6
Table 2-C IDU-to-ODU Cable Assembly ............................................................................ 2-6
Table 2-D E1/T1 Line Wiring on DB78 ............................................................................. 2-11
Table 2-E Prefabricated DB78P Cable Wire List .............................................................. 2-12
Table 2-F 100-BaseT Wiring (RJ45)................................................................................. 2-13
Table 2-G Computer Port (Serial; Sub-D 9-Pin Female) .................................................. 2-14
Table 2-H NMS Connection (IP Interface) ........................................................................ 2-14
Table 2-I Fastener Torque Specifications ........................................................................ 2-16
Chapter 3 — Commissioning
Chapter 4 — Operation
Chapter 5 — Maintenance
Table 5-A Proteus AMT-L Firmware Files......................................................................... 5-14
List of Figures
Chapter 1 — Radio Description
Figure 1-1. Proteus AMT L-Series Radio ........................................................................... 1-1
Figure 1-2. IDU Chassis ..................................................................................................... 1-3
Figure 1-3. IDU Front Panel (see Table 1-D for call-out description) ................................. 1-5
Figure 1-4. Proteus AMT L-Series ODU........................................................................... 1-10
Figure 1-5. RF Unit Features ........................................................................................... 1-11
Figure 1-6. Low Profile Antennas ..................................................................................... 1-12
Figure 1-7. 1.2- and 1.8m Antennas ................................................................................ 1-12
Figure 1-8. Signals Multiplexed onto the IDU-to-ODU Cable .......................................... 1-14
Figure 1-9. Interfaces to Radio Management Applications .............................................. 1-16
Chapter 2 — Installation
Figure 2-1. IDU Power Connection for -48V Input.............................................................. 2-9
Figure 2-2. IDU Power Connection for +24V Input............................................................. 2-9
Figure 2-3. Connecting Power Protection Devices........................................................... 2-10
Figure 2-4. Prefabricated DB78P Cable........................................................................... 2-12
Figure 2-5. Single ODU Mounting Dimensions ................................................................ 2-17
Chapter 3 — Commissioning
Figure 3-1. Typical Antenna Side Lobes ........................................................................... 3-6
Chapter 4 — Operation
Figure 4-1. Simplified Radio Link Diagram......................................................................... 4-1
Figure 4-2. IDU Functional Block Diagram......................................................................... 4-2
Figure 4-3. Line Interface Functions .................................................................................. 4-3
Figure 4-4. Multiplexing Data Lines and Overhead Channels............................................ 4-4
Figure 4-5. Outdoor Unit Block Diagram ............................................................................ 4-7
Figure 4-6. ODU Duplex Operation .................................................................................... 4-8
Figure 4-7. User Interface Functions.................................................................................. 4-9
Figure 4-8. Craft Terminal Interface Radio Management Software Outline...................... 4-11
Figure 4-9. Element Manager Radio Management Software Outline............................... 4-12
Chapter 5 — Maintenance
Figure 5-1. IDU Power Supply .......................................................................................... 5-8
Figure 5-2. IF Board in the IDU .......................................................................................... 5-9
Figure 5-3. IF Board .......................................................................................................... 5-9
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.
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.
System Components
In-door units fit in one The Proteus AMT L-Series radio is a compact split-mount configuration. An
rack space (1RU). RF indoor unit that mounts in a single rack space (1RU) provides signal pro-
units mount directly to cessing at QPSK or 8PSK modulation to convert digital line signals to, and
the antenna using
press-fit adapters. from, intermediate frequency (IF) signals.
IDUs match modulation ODUs operate in the 7/8, 10, 11, 13, 15, 18, 23, 26, 38-GHz frequency bands
to data-rate and using ETSI (International) and ANSI (North American) RF channel plans
bandwidth. (Appendix A).
Current-model radios Current model radios use a universal IDU that handles all modes of opera-
include IDUs that handle tion – modulation options, scalable capacity, and voice and data interfaces.
all modes of bandwidth, Software license keys set radio capacity and traffic type (Table 1-E). Radio
modulation, and
capacity. Your radio is management software maintains your radio configuration license
licensed to the mode you (see “Radio Management” on page 1-15).
purchase.
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
Early-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.
Chassis
The 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.
erence necessary for reliable radio operation. The IDU front panel includes
ground connection points to connect a suitable ground bus.
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 The main and IF board of the IDU handles all operating modes and band-
current-model IDUs can widths. Software sets data capacity and bandwidth – you receive a software
handle all modes. A license for the configuration you purchase (see “Radio Capacity Configura-
software license key
enables each mode. tion” on page 1-7).
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)
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
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.
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
2E1 4DS1
QPSK
100BT 2DS1 100BT QPSK
3.5 MHz 4E1 100BT
2E1 100BT 8PSK 5 MHz 8DS1
100BT 4DS1 100BT
8PSK
4E1 2DS1 100BT
2E1 100BT QPSK 100BT
100BT 8DS1
7 MHz 8E1 4DS1 100BT
QPSK
4E1 100BT 2DS1 100BT
8PSK
2E1 100BT 100BT
100BT 16DS1
10 MHz
8E1 12DS1 100BT
4E1 100BT 8DS1 100BT
QPSK 8PSK
2E1 100BT 4DS1 100BT
100BT 2DS1 100BT
14 MHz 16E1 100BT 100BT
12E1 100BT 16DS1 100BT
8E1 100BT 8PSK 12DS1 100BT
4E1 100BT 8DS1 100BT
QPSK
2E1 100BT 4DS1 100BT
16E1 2DS1 100BT
12E1 100BT 100BT
20 MHz
8E1 100BT 16DS1 100BT
QPSK
4E1 100BT 12DS1 100BT
2E1 100BT 8DS1 100BT
8PSK
100BT 4DS1 100BT
28 MHz
16E1 100BT 2DS1 100BT
12E1 100BT 100BT
8E1 100BT 16DS1 100BT
8PSK
4E1 100BT 12DS1 100BT
2E1 100BT 8DS1 100BT
QPSK
100BT 4DS1 100BT
2DS1 100BT
100BT
28 MHz
16DS1 100BT
12DS1 100BT
8DS1 100BT
8PSK
4DS1 100BT
2DS1 100BT
100BT
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
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.
Mounting latches
Antenna
RF Unit
Appendix E describes The RFU mounts to the antenna with latches, so it can be replaced without
alternate ODU mounting tools or affecting antenna alignment.
configuration - offset and
rack mounting.
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).
ANTENNA
POLARIZATION INTERFACE
MARK
LOCKABLE
LATCH
MOUNTING MOUNTING
CLAMPS CLAMPS
LOCKABLE N-TYPE
LATCH INPUT/OUPUT
(TO/FROM IDU)
AGC VOLTAGE
BACK SIDE VIEW FRONT CONNECTION
(FACES ANTENNA)
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.
Appendix E describes All antenna include an applicable radio interface flange and mounting hard-
options for separate ware. Antenna mounting hardware is a single bracket that accommodates
antenna and RF unit left or right hand mounting and to a tower or pole.
placement - offset and
rack mounting.
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.
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.
DATA LINK
5.5 MHz Up 350 MHZ
140 MHZ
DC 10 MHz Down IF Up
IF Down
CABSPE.VSD
Radio Management
All 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:
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.
Element Manager
On PC via Ethernet
Element Manager
On PC via Serial
Craft Terminal /
Command Line Interface
VT100 via Serial
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 Connections
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 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.
Use RIP for networks of moderate size within the following limitations:
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).
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.
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.
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.
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.
System Specifications
Proteus 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.
The first few tables cover general specifications. Subsections that follow list
specifications for radios that use ETSI and ANSI bandwidths.
Table 1-O lists transmit power for all data rates and bandwidths.
Table 1-O RF Transmit Power
RF Unit TX Power*
QPSK 8PSK
7/8 GHz 25 dBm 21dBm
11, 13, 15, 18 GHz 24 dBm 20 dBm
23 GHz 22 dBm 19 dBm
26 GHz 22 dBm 18 dBm
38 GHz 20 dBm 16 dBm
*
Maximum TX power setting. Actual output power will be ±1dB at the
antenna flange. Minimum TX power setting must be no less than -4dBm.
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.
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.
Installation Information
This material covers This chapter outlines physical installation of a non-protected Proteus
physical installation of a AMT L-Series radio. See Chapter 3, Commissioning, to setup the radio
non-protected radio. See and start traffic; see Appendix F for hot-standby radio installation.
Chapter 3 to setup and
initialize the radio. 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
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.
Grounding
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.
Unpacking Equipment
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 The RF unit is set as a transmit low- or high-band unit. RF units use a di-
range of its diplexer. Spares plexer instead of band-pass filters. Sub-band and transmit/receive spac-
come in sets that include the ing (low/high band) are fixed and must be specified at time of order. If
high- and low-band units purchasing and storing spares, store LB/HB sets for each frequency. RF
(go and return frequencies
unit synthesizers tune through the entire half-band of its frequency plan,
of each channel 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.
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.
• 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.
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.
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.
Ground the IDU to facility Ground the IDU chassis to the facility grounding system to minimize the
ground to prevent damage likelihood of damage from lightning strikes and the impact of electro-
to equipment and ensure magnetic- and radio frequency-interference (EMI/RFI). Grounding sys-
reliable operation. 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 Power
Power supplies must The IDU power connector is a 3-pin Phoenix connector. The mating
handle radio in-rush plug, 3024080-25, ships in the install kit (Table 2-A) with the radio. To
current≥8A up to 3ms. 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 Both the -48V and +24V power supplies require a ground reference to
to handle the in-rush operate. Mounting screws ground a unit that you mount in a grounded
current: ≥6A with trip EIA rack or enclosed cabinet. Otherwise, you must connect "ground"
characteristic 'C' or slower. (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 DC input to the 48V power supply will be between -40 to -60 Vdc (nom-
a power protection device. 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.
Ground '+' of
48V supply to set
ground refer-
ence.
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
Ground '-' of
24V supply to
set ground ref-
erence.
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.
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 Plan power devices — power supplies, fuse panels, breakers, un-inter-
the radio in-rush current. 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.
6A SLO-BLO
Battery IDU
Pack
48V/24V If using a breaker,
use ≥6A trip rating 'C'
or slower.
48V
UPS AC/DC IDU
Pin Signal Ch. Pin Signal Ch. Pin Signal Ch. Pin Signal Ch.
1 TXT 15 21 TXR 15 40 TXT 16 60 TXR 16
2 RXT 15 22 RXR 15 41 RXT 16 61 RXR 16
3 GND 23 TXT 13 42 GND 62 TXT 14
4 TXR 13 24 RXT 13 43 TXR 14 63 RXT 14
5 RXR 13 25 GND 44 RXR 14 64 GND
6 TXT 11 26 TXR 11 45 TXT 12 65 TXR 12
7 RXT 11 27 RXR 11 46 RXT 12 66 RXR 12
8 GND 28 TXT 9 47 GND 67 TXT 10
9 TXR 9 29 RXT 9 48 TXR 10 68 RXT 10
10 RXR 9 30 GND 49 RXR 10 69 GND
11 TXT 7 31 TXR 7 50 TXT 8 70 TXR 8
12 RXT 7 32 RXR 7 51 RXT 8 71 RXR 8
13 GND 33 TXT 5 52 GND 72 TXT 6
14 TXR 5 34 RXT 5 53 TXR 6 73 RXT 6
15 RXR 5 35 GND 54 RXR 6 74 GND
16 TXT 3 36 TXR 3 55 TXT 4 75 TXR 4
17 RXT 3 37 RXR 3 56 RXT 4 76 RXR 4
18 GND 38 TXT 1 57 GND 77 TXT 2
19 TXR 1 39 RXT 1 58 TXR 2 78 RXT 2
20 RXR 1 59 RXR 2
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.
Connecting Ethernet
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 Table 2-F 100-BaseT Wiring (RJ45*)
Appendix D describes. 2-port bridge
Pin Signal I/O Pin Signal I/O 8 1
1 Rx + I 5 GND
2 Rx – I 6 TX – O
3 Tx + O 7 GND
4 GND 8 GND
* See “Cable and Connector Considerations” on page 2-2.
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 Table 2-G Computer Port* (Serial; Sub-D 9-Pin Female)
through. Pin Signal I/O
1 NC
2 TXD O
3 RXD I
4 NC
5 GND
6 NC
7 NC
8 NC
9 NC
* Wire 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.
Table 2-H NMS Connection* (IP Interface)
Pin Signal I/O IP NMS CROSSOVER CABLE
1 Tx + O
2 TX – O
8 1
3 RX + I
4 NC
5 NC
6 RX – I 1 8
7 NC
8 NC
* Use a shielded RJ45 crossover cable when connecting a computer to
either NMS port, or when cabling from one IDU to another.
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.
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.
• 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
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:
Dim B
Dim C
Dim D
Dim C ODU
Dim F
AGC ACCESS AREA
Step 3: Move the hardware around the pipe so the antenna faces the final
azimuth direction. Tighten after antenna alignment is complete.
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.
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.
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.
Power circuits must handle • no shorts exist between ground and the pins using an ohm-meter
in-rush current as the • all connectors are secure
Installation chapter
(page 2-10) describes. • 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.
Once you configure your radio backup the configuration to file using
BACKUP CONFIGURATION from the EM File menu.
This procedure should have been done after ODU installation, however
this section repeats the steps for convenience.
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
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.
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.
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.
You can set transmit radio frequency at the local site only as follows:
1. Open Configuration from the main menu
2. Select ODU
3. Enter the transmit frequency for the NE radio. The IDU automatically
sets receive frequency.
Setting Tributaries
To 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 5. From the Payload menu of CTI select TRIBUTARY CONFIGURATION, or
interface in Element from EM select LIM A/B1 TRIBUTARIES, to set individual lines to
Manager. equipped or unequipped. The IDU monitors equipped channels for loss
of signal (LOS) while unequipped channels pass traffic without monitor.
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 >
The BERT dialog displays the bit error rate, or check the G.826 statistics
of the Performance window.
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.
Data Data
IDU ODU ODU IDU
Lines Lines
IDU
Encoder/
TX MUX
MOD
TX BUS
DB78
I/O
Connector RX BUS
IF Board
PROCESSOR BUS
Cable/MUX
& AGC
PROCESSOR BUS
RX BUS
TX BUS
Decoder/
RX DEMUX
DEMOD
TX BUS
Ethernet AGC
I/O Detect
Connector
RX BUS
NMS
Connector
PROCESSOR BUS
Mgmt Power
Serial Supply ODU DC POWER
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
To Mainboard
Tx Bus
Line
Transformers Interface Rx Bus
Rx FIFO-n
Signal Multiplexing
The multiplexer, Figure 4-4, addresses the line interface FIFOs through
transmit and receive buses using transaction-start pulses. All reads or
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.
Buffer/Control Line
Ethernet Bridge VHDL
Multiplex
Interface Buffer Rx Bus
Channels
Management
Tx Bus
Term-Term CH.
Overhead
Interface
Channel
(9.6 kbps)
IPOA CH.
(64 kbps)
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.
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.
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.
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.
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.
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).
RADIO MANAGEMENT
CHANNELS
TCP/UDP
NMS/SNMP (Ethernet)
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,
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.
1. Current Alarms Radio Select 1. Aggregate Local Loopback 1. IDU 1. Download Files
Radio select 1. Last Second Radio select Radio select Radio select
Figure 4-8.
2. Latched Alarms 2. Last Minute 1. Agg Local Loopback 1. Radio Name 1. Begin Download
Radio select 3. Last Hour 2. Agg Loopback Time 2. Inventory 2. Flash Destination [NA]
3. Alarm Log 4. Last Day 2. Aggregate BER Test 3. License Key 3. TFTP File Name [lc_app.mnz]
Radio select 6. Last Week Radio select 4. Admin Password 4. TFTP Server Address
Clear All Agg BER Results 5. Guest Password 2. Copy Image (Secondary to
1. Show Log Elapsed Sec.
1. Agg BER Test Mode 6. Set Clock
2. Reset Log Available Sec. Primary)
7. Craft Port Rate
4. Change Log Errored Sec. 2. Agg BER Test Results 3. Copy Image (Primary to
8. NMS Speed
Severely Errored Sec.
Page 4-11
Page 4-12
Operation
Figure 4-9.
Connect Alarms RF Statistics Inventory ODU Mute IDU Copy Image
NE/FE NE/FE Tx Power Image Booted TX control and timer Radio name & location Source
Disconnect Test Settings min/max/avg. ODU Serial/Firmware Ver. Contact Destination
NE/FE NE/FE RSL IDU Serial/Firmware Ver. Loopback Date/Time
Backup Configuration Event Log min/max/avg. IF Board Type/Serial Digital aggregate License Key Download Firmware
Alarm & Events Fade Margin LIM A/B Type and Serial Line (tributaries) Admin Password
Restore Configuration w/ save to file feature Full Info Table / Save to File Guest Password Reboot NE Radio
G.826 Statistics BERT Craft port baud rate primary image
Exit NE/FE Performance LinkView BER test for ODU secondary image
(based on G.826) On screen radio graphic aggregate data path TX Frequency all radios
of performance and inventory or tributaries TX Power
History ATPC mode Reboot FE Radio
Configure, RSL set point primary image
(display and save TX mute & timeout secondary image
performance data) PAYLOAD all radios
Historical Data Table Installed
BW Restore factory defaults
LIM A/B Type
Current
Modulation
BW
LIM A/B Type
Proposed
BW
LIM A/B Type
LIM A Tributaries
Equipped/Unequipped
Encoding
LIM B (100BT)Tributary
Equipped/Unequipped
IP Addresses
LAN
WAN
Default gateway
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.
Support Contacts
Include the RA number on the inside and on the outside of the package.
For out of warranty repairs include a purchase order.
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.
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
--------------------------------------------------
Configuration Menu
1. IDU
2. ODU
3. Payload / Modulation
4. IP
5. Alarms
6. Reset to factory Settings
0. Exit
Radio 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. Exit
Radio A, No Alarms, Link Up >
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.
--------------------------------------------------
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. Exit
Radio 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
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.
License key is unique to All license keys are unique to one IDU. The IDU verifies license key to
one IDU and identifies its mainboard serial number. Before upgrading a license key ensure that
your IDU by mainboard the upgrade matches the mainboard serial number using the radio the in-
serial number.
ventory screen.
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. Exit
Radio A, No Alarms, Link Up > 3
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.
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.
IDU
RFI/EMI
2A fuse Ferrite Bead
To Cable IDU/
ODU
-48V
Surge
Protector
The power supply fuse mounts on a fuse clip in the front of the power
supply. To replace the fuse:
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.
The power supply (Figure 5-1) mounts on the left side of the chassis. To
replace the power supply:
The IF board-to-mainboard Early-model radios have a fixed occupied bandwidth. Changing occu-
connection is delicate. Use pied bandwidth requires replacing the IF board. Figure 5-2 shows the lo-
care when removing the IF cation of the boards in the IDU chassis.
board.
Power
Supply
Main Board BACKUP
BATTERY
IF Board
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.
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.
Get a free trial version of a Load the compressed image file (*.mnz) through the Ethernet NMS port
TFTP server at using any networked PC running TFTP server software. Configure the
www.solarwinds.net TFTP server according to the product instructions.
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.
Get a free trial version of a Load the compressed image file (*.mnz) through the Ethernet NMS port
TFTP server at using any networked PC running TFTP server software.
www.solarwinds.net.
Download Files and Reboot Radio
1. Log in to IDU
2. From main menu, select 5-Utilities
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. Exit
Radio A, No Alarms, Link Up >
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.
Bootloader loads files 2. After you stop the boot, Bootloader selections open.
to the IDU only from
1. Force boot of primary image
the local serial port.
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
7. Download new FPGA image 2 and reboot
8. Download new FPGA image 3 and reboot
9. Change CRAFT port baud rate and reboot
0. Exit
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
FPGA images based on radio bandwidth options are separate image files
as Table 5-A shows.
Table 5-A Proteus AMT-L Firmware Files*
File Type P/N TFTP File Bootloader File
Bootloader 4600067-01 not applicable LC_Boot.hex
4600068-01_1.hex†
Application Code 4600068-01 LC_App.mnz
4600068-01_2.hex
‡
7MHz E1 FPGA 4600071-01 4600071-01_.MNZ 4600071-01_.hex
14MHz E1 FPGA 4600072-01 4600072-01_.MNZ 4600072-01_.hex
28MHz E1 FPGA 4600073-01 4600073-01_.MNZ 4600073-01_.hex
5MHz DS1 FPGA 4600074-01 4600074-01_.MNZ 4600074-01_.hex
10MHz DS1 FPGA 4600075-01 4600075-01_.MNZ 4600075-01_.hex
25MHz DS1 FPGA 4600076-01 4600076-01_.MNZ 4600076-01_.hex
2.5MHz DS1 FPGA 4600079-01 4600079-01_.MNZ 4600079-01_.hex
3.5MHz E1 FPGA 4600080-01 4600080-01_.MNZ 4600080-01_.hex
*. For current-version IDU on the product CD or from microwavenetworks.com.
†. Use either _1 or _2.
‡. File name includes revision level shown here as an underscore.
Serial load of the 3. Set the craft port baud rate to the highest rate of the connected serial
uncompressed terminal.
image files is 4. Select the destination (e.g., 4. Download new secondary image
slow. and reboot)
Your Selection: 4
Please send the file over the serial port
(you may have to press 'CTRL-Z' when the file download
completes)
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!
Maintenance Checks
Periodic Maintenance
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 Verify RSL (receive signal strength). Low RSL, or AGC voltage, that
up to -90 dBm, and does not stays low can mean antenna misalignment, RF path obstruction, decrease
accurately measure RSL for in transmitter power, or a reduction in receiver sensitivity. Ignore minor
radios operating beyond
-90 dBm. 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
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.
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.
7GHz
8GHz
For reference; contact MNI about availability.
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-J 11GHz 490 MHz T/R Spacing
TX Lower TX Upper RX Lower RX Upper
Sub-Band ODU P/N
Limit, MHz Limit, MHz Limit, MHz Limit, MHz
LB1 63-110490-00111-6100 10675 10855 11165 11345
HB1 63-110490-10111-6100 11165 11345 10675 10855
LB2 63-110490-00211-6100 10795 10975 11285 11465
HB2 63-110490-10211-6100 11285 11465 10795 10975
LB3 63-110490-00311-6100 10915 11095 11405 11585
HB3 63-110490-10311-6100 11405 11585 10915 11095
LB4 63-110490-00411-6100 11035 11215 11525 11705
HB4 63-110490-10411-6100 11525 11705 11035 11215
*LB-LOW BAND; HB-HIGH BAND
13GHz
15GHz
18GHz
23GHz
38 GHz
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).
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).
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).
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).
Overview
A 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
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.
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:
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 Tables
Figure C-2 shows the major Proteus AMT SNMP objects.
Status–view link or radio status.
Performance–monitor radio
performance statistics.
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.
Key Features
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
Basics
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.
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.
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 Descriptions
Menu Description
Connect opens when EM opens or
when selected. Set the connection as
serial or Ethernet.
Default passwords are:
Guest – no password
Admin – mni
Disconnect lets you close the connec-
tion.
The RESTORE Backup Configuration lets you save
CONFIGURATION your radio setup to a configuration file
command opens a restore (.cfg) that you can load to another, or
options box. The RESTORE replacement, radio.
PASSWORDS option is
Restore Configuration lets you load a
typically not used. The
specific radio configuration file.
option restores
passwords that you You can also load configuration files to
manually edit in your EM in Demo mode for validation and
backup file. If not troubleshooting.
manually entered, EM Alarms and Test Settings displays are
sets passwords as three identical for near- and far-end radios,
asterisks (***). 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 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.
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.
Type HELP and press ENTER for a list of available command. Enter HELP
MORE for an on-screen description of available commands.
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.
--------------------------------------------------
MENU TITLE Main Menu
1. Alarms
2. Performance
MENU SELECTION 3. Test
4. Configuration
5. Utilities
0. Exit
Radio A, No Alarm, Link Up >
Alarm Menu
--------------------------------------------------
Alarm Menu
1. Current Alarms
2. Latched Alarms
3. Alarm Log
4. Change Log
5. Clear All Latched Alarms
0. Exit
Radio A, No Alarm, Link Up >
Performance 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. Exit
Radio A, No Alarms, Link Up >
Test Menu
--------------------------------------------------
Test Menu
1. Aggregate Local Loopback
2. Aggregate BER Test
3. Tributary Loopback
4. Tributary BER Test
5. ODU Mute
0. Exit
Radio A, No Alarm, Link Up >
Configuration Menu
--------------------------------------------------
Configuration Menu
1. IDU
2. ODU
3. Payload / Modulation
4. IP
5. Alarms
6. Reset to factory Settings
0. Exit
Radio A, No Alarms, Link Up >
Utility Menu
--------------------------------------------------
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. Exit
Radio A, No Alarms, Link Up >
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: admin
Password: ***
*************************************************************
*
* 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
--------------------------------------------------
Alarm Menu
1. Current Alarms
2. Latched Alarms
3. Alarm Log
4. Change Log
5. Clear All Latched Alarms
0. Exit
Radio A, No Alarm, Link Up > 1
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.
--------------------------------------------------
Current Alarms
1. Near End [Normal]
2. Far End [Normal]
0. Exit
Radio A, No Alarm, Link Up > 3
MAJOR: ON
IF Board PLL Lock
Modem Receive Fail
Modem Rx Frame Loss
Rx BER > 10^-3
MINOR: 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
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.
--------------------------------------------------
Near End Alarm Log Menu
1. Show Alarm Log
2. Reset Alarm Log
0. Exit
Radio A, No Alarm, Link Up > 1
2005/02/24 11:29:55, Radio A, (set), ODU Telemetry Alarm, I: 33, O: 0
2005/02/24 11:29:55, Radio A, (set), IF Board PLL Lock, I: 33, O: 0
2005/02/24 11:29:54, Radio A, (set), Tributary 8 RX LOS, I: 33, O: 0
2005/02/24 11:29:54, Radio A, (set), Tributary 6 RX LOS, I: 33, O: 0
2005/02/24 11:29:54, Radio A, (set), Tributary 3 RX LOS, I: 33, O: 0
2005/02/24 11:29:54, Radio A, (set), Tributary 1 RX LOS, I: 33, O: 0
2005/02/24 11:29:54, Radio A, (set), AIS Inserted on Tributaries
2005/02/24 11:29:54, Radio A, (set), Custom BER Level, I: 33, O: 0
2005/02/24 11:29:54, Radio A, (set), Rx BER > 10^-6, I: 33, O: 0
2005/02/24 11:29:54, Radio A, (set), Rx BER > 10^-3, I: 33, O: 0
2005/02/24 11:29:54, Radio A, (set), Modem Receive Fail, I: 33, O: 0
2005/02/24 11:29:54, Radio A, (set), Major Alarm - Latched, I: 33, O: 0
2005/02/24 11:29:54, Radio A, (set), Major Alarm Summary, I: 33, O: 0
2005/02/24 11:29:54, Radio A, (set), Modem Rx Frame Loss, I: 33, O: 0
2005/02/24 11:29:54, Radio A, (set), Minor Alarm - Latched, I: 33, O: 0
2005/02/24 11:29:54, Radio A, (set), Minor Alarm Summary, I: 33, O: 0
End
--------------------------------------------------
Near End Change Log Menu
1. Show Change Log
2. Reset Change Log
0. Exit
Radio A, No Alarm, Link Up > 1
2005/02/24 14:46:47, 29, Admin, 172.16.99.22, Command Processor Command
2005/02/24 14:44:52, 3, Admin, 172.16.99.22, Command Processor Command
2005/02/24 14:44:24, 3, Admin, 172.16.99.22, Command Processor Command
End
Performance
-------------------------------------------------
Performance
1. Near End
2. Far End
3. Reset All Stats
0. Exit
Radio 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. Exit
Radio A, No Alarms, Link Up >
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.
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)
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.
On the performance statistics menus the All Statistics selection lists all
G.826 statistics and the significant RF performance measurements.
Near End Performance (Custom)
Near End
Elapsed Seconds: 172194
Available Seconds: 0
Unavailable Seconds: 172194
Errored Seconds: 0
Severely Errored Seconds: 0
Errored Seconds Ratio: 0.00e+00
Sev Errored Seconds Ratio: 0.00e+00
Total Codewords: 0
Bit Error Rate: 0.00e+00
Back Bit Error Rate: 0.00e+00
Current RSL: 0
Fade Margin: 70
Transmit Power: 0
(CTRL-C to exit)
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 Uploaded performance history files go your TFTP server (not provided)
TFTP server at at the interval you set, or you can request a manual upload anytime.
www.solarwinds.net
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 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. Exit
Radio 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.
-------------------------------------------------
Test Menu
1. Aggregate Local Loopback
2. Aggregate BER Test
3. Tributary Loopback
4. Tributary BER Test
5. ODU Mute
0. Exit
Radio A, No Alarm, Link Up >
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.
-------------------------------------------------
Tributary Loopback
1. Near End
2. Far End
0. Exit
Radio A, No Alarm, Link Up > 1
--------------------------------------------------
Near End Tributary Loopback Menu
1. Tributary Local Loopback
2. Tributary Remote Loopback
0. Exit
Radio A, No Alarm, Link Up >
Local Aggregate
Loopback
IDU NE/FE Local
Tributary
Loopback ODU
Processing
Multiplex Coding
LIU and and RF
IF
Frame Modem Processing
NE/FE Remote
Tributary
Loopback
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. Exit
Radio 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. Exit
Radio 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. Exit
Radio A, No Alarm, Link Up >
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. Exit
Radio 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. Exit
Radio A, No Alarm, Link Up > 1
Configuration
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.
--------------------------------------------------
Near End IDU
1. Near End (Local) [Radio A]
2. Far End [Radio B]
0. Exit
Radio 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. Exit
Radio A, No Alarms, Link Up >
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.
Near End
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.
--------------------------------------------------
ODU
1. Near End [13120.000 MHz]
2. Far End [12854.000 MHz]
0. Exit
Radio 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. Exit
Radio A, No Alarm, Link Up >
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.
--------------------------------------------------
IP
1. Near End (Local) [172.2.1.2]
2. Far End [172.3.1.1]
0. Exit
Radio 5, No Alarms, Link Up >
--------------------------------------------------
Near End IP Configuration Menu
1. LAN Interface [172.2.1.2]
2. WAN Interface [3.3.3.1]
3. Routing Table
0. Exit
Radio 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. Exit
Radio A, No Alarms, Link Up > 1
Please enter new value for LAN Address (in dotted decimal):
Utilities
Get a trial version of an IDU and line code downloads to programmable logic in the IDU. The
TFTP server at source port is the Ethernet port from a TFTP server. Use any networked
http://www.solarwinds.net PC running TFTP server software to download firmware to the radio.
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. Exit
Radio 5, No Alarms, Link Up >
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. Exit
Radio A, No Alarms, Link Up > 5
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. Exit
SWLab-100, No Alarms, Link Up > 5
--------------------------------------------------
Reboot To Primary Image
1. Near End (Local)
2. Far End
3. All Radios
0. Exit
Radio A, No Alarms, Link Up > 3
Are you sure you wish to reboot all radios (y/n)? y
Rebooting Online Far End Radio ...
Rebooting myself, good bye ...
Overview
Use this section to set The wide area network (WAN) interface, or IPO-Air (Internet Protocol
up and implement your over the air), channel is a dedicated channel in the microwave communi-
radio network. 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 Communication
To communicate via IP, Both radios in a link must have IP addresses on the same subnet to com-
radios in a link must municate. The address and subnet mask determine the subnet. Subnet
have IP addresses on mask is a description of values within an IP address unique to the subnet.
the same 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
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.
--------------------------------------------------
Configuration Menu
1. IDU
2. ODU
3. Payload / Modulation
4. IP
5. Alarms
6. Reset to factory Settings
0. Exit
Radio A, No Alarm, Link Up > 4
--------------------------------------------------
IP
1. Near End (Local) [172.2.1.2]
2. Far End [172.3.1.1]
0. Exit
Radio 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. Exit
Radio 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. Exit
Radio A, No Alarms, Link Up >
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.
IP Data Routing
The 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.
IP Configuration Menu
1. LAN Interface [172.16.20.201]
2. WAN Interface [172.40.200.201]
4. Routing Table
0. Exit
Radio 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. Exit
Radio A, No Alarms, Link Up >
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
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.
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 Static routes are routes that you add to a routing table. Static routes stay
PCs to monitor radios in the routing table across power-ups until the you delete them. The ex-
on a different subnet. ception is when an interface goes down and all the routes to that interface
See the following page. 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.
forward packets to the LAN interface of BotRadio. Once done, you can
ping address 172.18.200.101 from the PC.
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. Exit
Radio A, No Alarms, Link Up >
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.
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.
Ethernet connection
microwave link
LAN 172.16.5.2 172.16.13.1 LAN
WAN 172.16.6.1 172.16.12.2 WAN
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.
Use CUSTOM To fix this problem, send a CUSTOM ADVERTISEMENT (using the radio
ADVERTISEMENT to management software) out of port 172.16.15.2. This advertisement will
extend a RIP enabled be the network 172.17.0.0/16, with a metric of 1 (at 172.16.15.2). By the
networks. 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.
Overview
RF 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 Mounting
Use antennas from a variety Use the ODU offset mounting kit, Table E-A and Figure E-1, to mount a
of vendors that use a non-protected RF unit on a pole separate from an antenna that uses a
standard rectangular standard waveguide feed. Employ the offset ODU option where a Pro-
waveguide interface. 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 Kit
Description P/N
7/8-GHz ODU Offset Mounting Kit, Circular I/O 8708271-07
11-GHz ODU Offset Mounting Kit, Circular I/O 8708271-11
13-GHz ODU Offset Mounting Kit, Rect. I/O 8708271-00
15-GHz ODU Offset Mounting Kit, Rect. I/O 8708271-01
18-GHz ODU Offset Mounting Kit, Circular I/O 8708271-18
23/26-GHz ODU Offset Mounting Kit, Circular I/O 8708271-23
38-GHz ODU Offset Mounting Kit, Circular I/O 8708271-38
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.
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.
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.
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 Waveguide
Adapters 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.
Dimension (inch)
Waveguide
ODU A B C D E Flex Waveguide Type
Flange
screw
7/8 GHz 1.474 1.352 1.178 0.900 8-32 Circular - WR112 PBR84
11 GHz 1.280 1.220 0.770 0.400 8-32 Circular - WR90 PBR100
13 GHz 1.122 1.040 0.750 0.375 6-32 Rectangular - WR75 PBR120
15 GHz 0.956 0.994 0.622 0.311 6-32 Rectangular - WR62 PBR140
18 GHz 0.670 0.640 0.420 0.170 4-40 Circular - WR42 PBR220
23/26 GHz 0.670 0.640 0.384 0.250 4-40 Circular - WR42 PBR220
38 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 lists some of the flexible waveguide available for use with the
ODU offset mounting option. Contact MNI sales for different lengths.
Overview
A 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.
Protection switching is The Redundancy Switch Unit (RSU) handles the switch between main
non-reverting—system will and standby units. Both transmit and receive signal paths switch to-
not switch to original radio
once alarms clear. gether. Figure F-1 shows the protected radio configuration.
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.
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.
IDU
(MAIN)
CONTROL
DATA
& STATUS
ODU
USER (MAIN)
DATA HOT
STANDBY COUPLER
SWITCH
ODU
(STANDBY)
CONTROL
DATA
& STATUS
IDU
(STANDBY)
HSB_OP.VSD
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].
IDU IDU
(STANDBY) (STANDBY)
ODU ODU
(STANDBY) (STANDBY)
5
RSU
RSU
1 ODU ODU
(MAIN) (MAIN)
4 2
1
3
IDU 3 IDU
(MAIN) (MAIN)
The current HSB coupler Hot-standby couplers come with an push-fit antenna interface fixed for
design comes vertically vertical polarization. Set horizontal polarization on the current coupler
polarized. An adapter kit is design by changing out the polarization adapter for a horizontally polar-
available for horizontal
polarization ized adapter. Ask for kit 8209282-xx; where 'xx' is frequency range of the
HSB coupler.
Original couplers came
with an antenna interface On early-model couplers you had to change the orientation of the RF unit
vertically polarized, and assembly (RFUs and coupler) relative to the fixed mounting position of
you rotated the complete the antenna, and, on ODUs at 15-GHz and below, also turn the transition
RF assembly for horizontal on the antenna.
polarization.
All antenna mounting hardware includes course and fine adjustment
points for azimuth and elevation.
IDU A
RSU
IDU B
An RSU switches customer Switches match IDU line types for ANSI or ETSI systems.
data.
• P/N 8209265-18, 16E1 Redundancy Switch Unit
Jumper cables link NMS • P/N 8209265-19, 16DS1 Redundancy Switch Unit
and ports of co-located
radios; see Table 2-L. 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 Auto-switching logic begins at the main terminal, but once switched
non-reverting and is not does not revert signals to the main path–even after alarms clear. On mul-
hitless. 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.
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
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.
1 2 34 5 6 7 8 9
Figure F-5. RSU Front Panel
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.
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.
Table F-D
Item 1. & 4
Table F-D
Item 2.
Table F-D
Item 3a.
3b 4 1 2 3a
Figure F-7. IDU to RSU Connections
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
Line ports are auto-sensing so the RSU does not need configuration.
Use the twisted pair sets of Line input and output signals connect with a DB78 female connector
your cable for each ring/tip provided in the installation kit (Table 2-A). Line signals (Table F-F) con-
signal of E1/DS1 lines. nect via twisted-pair wire to the E1/DS1 channels.
Do not untwist any pair
more than 12.7 mm (1/2
inch).
Table F-F E1/T1 Line Wiring on DB78
Female front panel con-
1 nector shown; mating
connector pins are the
mirror image
(Page F-10).
Pin Signal Ch. Pin Signal Ch. Pin Signal Ch. Pin Signal Ch.
1 TXT 15 21 TXR 15 40 TXT 16 60 TXR 16
2 RXT 15 22 RXR 15 41 RXT 16 61 RXR 16
3 GND 23 TXT 13 42 GND 62 TXT 14
4 TXR 13 24 RXT 13 43 TXR 14 63 RXT 14
5 RXR 13 25 GND 44 RXR 14 64 GND
6 TXT 11 26 TXR 11 45 TXT 12 65 TXR 12
7 RXT 11 27 RXR 11 46 RXT 12 66 RXR 12
8 GND 28 TXT 9 47 GND 67 TXT 10
9 TXR 9 29 RXT 9 48 TXR 10 68 RXT 10
10 RXR 9 30 GND 49 RXR 10 69 GND
11 TXT 7 31 TXR 7 50 TXT 8 70 TXR 8
12 RXT 7 32 RXR 7 51 RXT 8 71 RXR 8
13 GND 33 TXT 5 52 GND 72 TXT 6
14 TXR 5 34 RXT 5 53 TXR 6 73 RXT 6
15 RXR 5 35 GND 54 RXR 6 74 GND
16 TXT 3 36 TXR 3 55 TXT 4 75 TXR 4
17 RXT 3 37 RXR 3 56 RXT 4 76 RXR 4
18 GND 38 TXT 1 57 GND 77 TXT 2
19 TXR 1 39 RXT 1 58 TXR 2 78 RXT 2
20 RXR 1 59 RXR 2
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-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:
Dim G
Dim B
Dim C
ODU
ODU
ODU
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.
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.
Step 1: Observe the V label on the RF unit
housing. The V label must point up
for vertical polarization.
Overview
Table 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.