ProteusAMT RevU
ProteusAMT RevU
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.
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 Radio information in this manual.
Manual Organization
This manual is organized into the following sections.
Provides a quick look of how this manual presents our product information.
Table of Contents
Lists all chapters, sections, headings, and subheadings in the manual, as well
as where to find them.
Chapter 2–Installation
Chapter 3–Commissioning
Chapter 4–Operation
Describes signal flow through the radio, switching and loopback. Includes
instructions on using radio features.
Chapter 5–Maintenance
Table of Contents
Chapter 1 — Radio Description
Overview ....................................................................................................................... 1-1
Components........................................................................................................ 1-2
Configurations.................................................................................................... 1-2
Non-Protected Configuration.................................................................... 1-2
Hot-Standby (1:1) Protection.................................................................... 1-2
Indoor Unit .................................................................................................................... 1-4
Chassis................................................................................................................ 1-4
Front Panel ......................................................................................................... 1-5
Line Interface Modules ...................................................................................... 1-6
IDU Circuit Boards .......................................................................................... 1-11
Outdoor Unit................................................................................................................ 1-12
Radio Frequency Unit ...................................................................................... 1-12
Antenna ............................................................................................................ 1-14
Redundancy Switch Unit............................................................................................. 1-16
RSU Front Panel Features ................................................................................ 1-19
RSU Interconnect Cables ................................................................................. 1-21
IDU-to-ODU Interface Cable ...................................................................................... 1-22
Radio Management...................................................................................................... 1-23
Element Manager ............................................................................................. 1-23
EM Connections ..................................................................................... 1-24
SNMP ............................................................................................................... 1-24
SNMP Connection .................................................................................. 1-24
Text-Based Menu Interface.............................................................................. 1-25
Text-Based Interface Connection ........................................................... 1-25
Telnet................................................................................................................ 1-26
Telnet Connection................................................................................... 1-26
Engineering Orderwire (EOW) ................................................................................... 1-26
Specifications .............................................................................................................. 1-27
International Data Rates ................................................................................... 1-30
North American Data Rates ............................................................................. 1-33
Mixed Data Rates ............................................................................................. 1-37
Chapter 2 — Installation
Overview ....................................................................................................................... 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
Chapter 3 — Commissioning
Overview ....................................................................................................................... 3-1
Powering the Radio ....................................................................................................... 3-1
Verifying Radio Configuration ..................................................................................... 3-2
Aligning the ODU ......................................................................................................... 3-3
Course ODU Alignment..................................................................................... 3-4
Fine ODU Alignment ......................................................................................... 3-4
Set Final ODU Alignment ........................................................................ 3-4
Making Configuration Changes .................................................................................... 3-6
Configuring the ODU......................................................................................... 3-6
Set Transmit and Receive Frequency ....................................................... 3-6
Set Transmit Power Output ...................................................................... 3-6
Configuring the IDU .......................................................................................... 3-7
Set Capacity .............................................................................................. 3-7
Set Tributaries........................................................................................... 3-7
Chapter 4 — Operation
Overview ....................................................................................................................... 4-1
Basic Operation ............................................................................................................. 4-1
Line Interface ..................................................................................................... 4-2
Signal Multiplexing............................................................................................ 4-3
Service Channels ...................................................................................... 4-4
Management Channels.............................................................................. 4-5
Modulation and Coding...................................................................................... 4-5
IF Conversion and Multiplexing ........................................................................ 4-6
RF Conversion.................................................................................................... 4-7
Protection Switching ..................................................................................................... 4-8
Reverse Channel Switch..................................................................................... 4-9
User Interfaces............................................................................................................. 4-10
NMS / SNMP (Ethernet) .................................................................................. 4-10
MODEM / PPP (Serial IP) ............................................................................... 4-11
COMPUTER / CTI (Serial).............................................................................. 4-11
Management Software...................................................................................... 4-11
Chapter 5 — Maintenance
Overview ....................................................................................................................... 5-1
Customer Service Options............................................................................................. 5-1
Telephone Support ............................................................................................. 5-1
Repair and Exchange Services ........................................................................... 5-1
Technical Support Services................................................................................ 5-2
Maintenance .................................................................................................................. 5-3
Replacing IDU Components .............................................................................. 5-3
Replacing LIMs ........................................................................................ 5-3
Replacing the Power Supply Fuse ............................................................ 5-4
Replacing the Backup Battery .................................................................. 5-4
Replacing the Power Supply Board.......................................................... 5-5
Replacing IF Boards ................................................................................. 5-6
Replacing ODU RF Units .................................................................................. 5-7
Updating Firmware ............................................................................................ 5-8
Using EM to Update Firmware................................................................. 5-8
Using CTI to Update Firmware ................................................................ 5-9
Maintenance Checks.................................................................................................... 5-10
List of Figures
Chapter 1 — Radio Description
Figure 1-1. Proteus AMT Radio ......................................................................................... 1-1
Figure 1-2. Hot-Standby Configuration .............................................................................. 1-3
Figure 1-3. IDU Chassis and Components......................................................................... 1-4
Figure 1-4. IDU Front Panel ............................................................................................... 1-5
Figure 1-5. Line Interface Module (LIM) Interfaces ............................................................ 1-7
Figure 1-6. Proteus AMT ODU ......................................................................................... 1-12
Figure 1-7. RF Unit Features ........................................................................................... 1-13
Figure 1-8. Low Profile Antennas ..................................................................................... 1-14
Figure 1-9. 1.2- and 1.8m Antennas ................................................................................ 1-14
Figure 1-10. Hot-Standby ODU Mounting with Coupler ................................................... 1-15
Figure 1-11. Redundancy Switch Configurations with DB78 E1/DS1 Line Connector..... 1-17
Figure 1-12. Redundancy Switch Configurations with RJ48 E1/DS1 Line Connectors.... 1-18
Figure 1-13. RSU Front Panel-Left Side .......................................................................... 1-19
Figure 1-14. Line Interfaces of the Redundancy Switch Unit ........................................... 1-20
Figure 1-15. IDU to RSU Connections ............................................................................. 1-21
Figure 1-16. Signals Multiplexed onto the IDU-to-ODU Cable ........................................ 1-22
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. 32E1/DS1 NP Configuration; Line Signal on DB78 ....................................... 2-12
Figure 2-5. Prefabricated DB78P Cable........................................................................... 2-14
Figure 2-6. 32E1/DS1 NP Configuration; Line Signal on RJ48 ........................................ 2-15
Figure 2-7. Handset ......................................................................................................... 2-17
Figure 2-8. IDU to RSU Connections ............................................................................... 2-20
Figure 2-9. RSU E1/DS1 Line Connections ..................................................................... 2-22
Figure 2-10. Non-Protected ODU Mounting Dimensions ................................................. 2-25
Figure 2-11. Protected ODU Mounting Dimensions ......................................................... 2-26
Figure 2-12. Early-Model 7-GHz ODU Pole Mount Hardware.......................................... 2-31
Chapter 3 — Commissioning
Figure 3-1. Typical Antenna Side Lobes ........................................................................... 3-5
Chapter 4 — Operation
Figure 4-1. Simplified Radio Link Diagram......................................................................... 4-1
Figure 4-2. Major Functions of the Proteus AMT Radio .................................................... 4-2
Figure 4-3. LIM Functions .................................................................................................. 4-2
Figure 4-4. IDU Signal Processing ..................................................................................... 4-3
Figure 4-5. Multiplexing Data I/O Lines .............................................................................. 4-3
Figure 4-6. Multiplexing Overhead Channels ..................................................................... 4-4
Chapter 5 — Maintenance
Figure 5-1. IF Board in the IDU.......................................................................................... 5-6
List of Tables
Chapter 1 — Radio Description
Table 1-A Typical Hot-Standby Switching Time ................................................................. 1-3
Table 1-B Front-Panel Features......................................................................................... 1-5
Table 1-C Line Interface Module Part Numbers................................................................. 1-6
Table 1-D PDH LIM Configurations.................................................................................... 1-8
Table 1-E Ethernet and PDH LIM Configurations .............................................................. 1-9
Table 1-F Major Components of the IDU ......................................................................... 1-11
Table 1-G RF Unit Part Numbers ..................................................................................... 1-13
Table 1-H RF Unit Connections ....................................................................................... 1-13
Table 1-I Redundancy Switche Units ............................................................................... 1-16
Table 1-J Common RSU Front-Panel Features ............................................................... 1-19
Table 1-K Hot-Standby Radio Interconnect Cables ......................................................... 1-21
Table 1-L IDU-to-ODU Cable Components...................................................................... 1-22
Table 1-M General Radio Specification............................................................................ 1-28
Table 1-N Environmental Specification ............................................................................ 1-29
Table 1-O Mechanical Specification................................................................................. 1-29
Table 1-P Power Specification ......................................................................................... 1-29
Table 1-Q Hot-Standby Branching Loss & Switch Time................................................... 1-29
Table 1-R RF Transmit Power.......................................................................................... 1-30
Table 1-S 2E1 to 1E3 System Specification .................................................................... 1-30
Table 1-T 20E1 to 32E1\2E3 System Specification ......................................................... 1-31
Table 1-U 100BaseT System Specification – International Bandwidth ............................ 1-31
Table 1-V 2 x 100BaseT* System – International Bandwidth........................................... 1-31
Table 1-W 2E1+100BaseT System Specification ............................................................ 1-31
Table 1-X 4E1+100BaseT System Specification ............................................................. 1-32
Table 1-Y 16E1+100BaseT System Specification ........................................................... 1-32
Table 1-Z RF Transmit Power .......................................................................................... 1-33
Table 1-AA 4DS1 to 24DS1 System Specification ........................................................... 1-33
Table 1-AB 28DS1\DS3 & 32DS1 System Specification.................................................. 1-34
Table 1-AC 2DS1+DS3 to 8DS1+DS3 System Specification........................................... 1-34
Table 1-AD 12DS1+DS3 to 2DS3 System Specification.................................................. 1-34
Table 1-AE 100BaseT System Specification – North American Bandwidths ................... 1-34
Table 1-AF 2 x 100BaseT* System – North American Bandwidths ................................. 1-35
Table 1-AG 2DS1+100BaseT System Specification ........................................................ 1-35
Table 1-AH 4DS1+100BaseT System Specification ........................................................ 1-35
Table 1-AI 8DS1+100BaseT System Specification......................................................... 1-36
Table 1-AJ 12DS1+100BaseT System Specifications ..................................................... 1-36
Table 1-AK 16DS1+100BaseT System Specifications.................................................... 1-36
Table 1-AL DS3+100BaseT System Specifications ......................................................... 1-36
Table 1-AM 2E1+2DS1 to 16E1+16DS1 System Specifications...................................... 1-37
Table 1-AN 2E1+DS3 to E3+DS3 System Specifications ................................................ 1-37
Chapter 2 — Installation
Table 2-A IDU-to-ODU Cable Components ....................................................................... 2-6
Table 2-B IDU-to-ODU Cable Assembly ............................................................................ 2-6
Table 2-C E1/DS1 Wiring (RJ48)..................................................................................... 2-11
Table 2-D E3/DS3 Wiring (BNC, 75-W) ........................................................................... 2-11
Table 2-E 100-BaseT Wiring (RJ45)................................................................................ 2-11
Table 2-F DB78 Line Signal Connector Wiring ................................................................ 2-13
Table 2-G Prefabricated DB78P Cable Wire List............................................................. 2-14
Table 2-H 16E1/DS1 Hot-Standby Wiring (HD, 100-pin) ................................................. 2-15
Table 2-I Modem Connection (IP Interface; Sub-D 9-Pin Male) ...................................... 2-16
Table 2-J Computer Port* (Serial; Sub-D 9-Pin Female) ................................................. 2-17
Table 2-K NMS Connection (IP Interface) ....................................................................... 2-17
Table 2-L OW1/2 (RJ45, 8-pin modular connection) ....................................................... 2-18
Table 2-M DTMF HANDSET (RJ-11, 4-pin)..................................................................... 2-18
Table 2-N AUX (26-pin Sub-D; High Density).................................................................. 2-19
Table 2-O RSU Interconnect Cables ............................................................................... 2-20
Table 2-P 100-BaseT Cabling Between IDU and RSU.................................................... 2-21
Table 2-Q Fastener Torque Specifications ..................................................................... 2-24
Chapter 3 — Commissioning
Table 3-A Redundancy Switch Unit Configuration Jumpers .............................................. 3-8
Chapter 4 — Operation
Table 4-A Typical Hot-Standby Switching Time................................................................. 4-9
Chapter 5 — Maintenance
Table A-N 7GHz, 154 MHz T/R Spacing; 140/350-MHz IF................................................ A-6
Table A-O 7GHz, 160 MHz T/R Spacing; 140/350-MHz IF ............................................... A-6
Table A-P 7GHz 161 MHz T/R Spacing; 140/350-MHz IF................................................. A-7
Table A-Q 7GHz 196 MHz T/R Spacing; 140/350-MHz IF ................................................ A-7
Table A-R 8GHz 119 MHz T/R Spacing; 140/350-MHz IF................................................. A-8
Table A-S 8GHz 208 MHz T/R Spacing; 140/350-MHz IF................................................. A-8
Table A-T 8GHz 266 MHz T/R Spacing; 140/350-MHz IF ................................................. A-8
Table A-U 8GHz 311.32 MHz T/R Spacing; 140/350-MHz IF............................................ A-8
Table A-V 11GHz 490 MHz T/R Spacing; 140/350-MHz IF............................................... A-9
Table A-W 11GHz 530 MHz T/R Spacing; 140/350-MHz IF.............................................. A-9
Table A-X 13GHz 266 MHz T/R Spacing; 140/350-MHz IF............................................... A-9
Table A-Y 15GHz, 315 MHz T/R Spacing; 140/350-MHz ................................................ A-10
Table A-Z 15GHz, 420 MHz T/R Spacing; 140/350-MHz IF ............................................ A-10
Table A-AA 15GHz, 490 MHz T/R Spacing; 140/350-MHz IF ......................................... A-10
Table A-AB 15GHz, 475 MHz T/R Spacing; 140/350-MHz.............................................. A-11
Table A-AC 15GHz, 640 MHz T/R Spacing; 140/350-MHz ............................................. A-11
Table A-AD 15GHz, 644 MHz T/R Spacing; 140/350-MHz ............................................. A-11
Table A-AE 15GHz, 728 MHz T/R Spacing; 140/350-MHz.............................................. A-11
Table A-AF 18GHz, 1010 MHz T/R Spacing; 140/350-MHz IF........................................ A-12
Table A-AG 18GHz, 1560 MHz T/R Spacing; 140/350-MHz IF ....................................... A-12
Table A-AH 23GHz, 1008 MHz T/R Spacing; 140/350-MHz ........................................... A-12
Table A-AI 23GHz, 1200 MHz T/R Spacing; 140/350-MHz ............................................. A-12
Table A-AJ 23GHz, 1232 MHz T/R Spacing; 140/350-MHz ............................................ A-13
Table A-AK 26 GHz, 800 MHz T/R Spacing; 140/350-MHz ............................................. A-13
Table A-AL 26 GHz, 1008 MHz T/R Spacing; 140/350-MHz ........................................... A-13
Table A-AM 38GHz, 700 MHz T/R Spacing; 140/350-MHz IF......................................... A-14
Table A-AN 38GHz, 1260 MHz T/R Spacing; 140/350-MHz IF ....................................... A-14
Overview
The Proteus AMT (Adaptive Modulation Transport) radio is a flexible
point-to-point digital microwave radio for 1.544- to 100-Mbps data. The
radio operates at frequencies from 7 to 38 GHz using 3.5- to 28-MHz
bandwidth.
Proteus AMT radios use a split indoor unit-outdoor unit (IDU/ODU) con-
figuration. Adaptive modulation and a range of plug-and-play line mod-
ules let you upgrade your link from low and medium capacity data traffic
to high speed traffic without replacing the radio.
Components
The automatic transmit power control (ATPC) feature allows the radio to
maintain a constant receive signal level (RSL) at the receive site by am-
plifying or attenuating the transmitter. You configure RSL threshold and
maximum TX power. Minimum power is fix to 30 dB below the speci-
fied output of your radio. APC mode keeps RSL within +3 dB of the set
point by stepping far-end transmit power ±1 dB.
Configurations
Non-Protected Configuration
The non-protected system is ideal for low-cost non-critical links. Each
terminal has only one IDU and one ODU. The RF and digital signals are
not protected against propagation and equipment faults. On equipment
faults or path failure the connection breaks until maintenance personnel
either repair the fault or reroute the path.
Hot-Standby (1:1) Protection
A hot-standby (HSB) 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
gether. Figure 1-2 shows the protected radio configuration.
once alarms clear.
Both radios operate at the same frequency. The main radio transmit path
connects via the through-arm of a coupler\combiner while the standby
radio connects via the coupled arm. Transmit power is 6.5-dB lower on
the standby path and 1.9-dB lower on the main path.
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 1-A
list the typical system switch times.
Table 1-A Typical Hot-Standby Switching Time
IF BW Manual Software Loss of Signal High IDU Power ODU Power
Switch (Online Request) (Data Input) BER Fail Fail
28 MHz 281.3 ms 289.1 ms 318.1 ms 432.2 ms 309.1 ms 221.3 ms
14 MHz 175.4 ms 161.2 ms 175.4 ms 281.9 ms 190.8 ms 159.2 ms
7 MHz 164.2 ms 170.3 ms 196.0 ms 190.6 ms 190.6 ms 181.7 ms
3.5 MHz 313.8 ms 374.4 ms 361.4 ms 162.2 ms 162.0 ms 186.7 ms
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.
ID U
(M AIN )
CONTROL
D AT A
& S T AT U S
ODU
USER (M AIN )
D AT A HOT
S T AN D B Y CO UPLER
S W IT C H
ODU
(S T AN D B Y )
CONTROL
D AT A
& S T AT U S
ID U
(S T AN D B Y )
H S B _O P .V S D
Indoor Unit
Chassis
The IDU chassis houses the main board, power supply, IF board,
front-panel board, and two plug-in line interface modules (LIMs, Figure
1-3). The aluminum chassis has heat sinks to dissipate heat.
Signal and power connectors and service indicators mount to the chassis
front panel. Front-access slots for plug-in LIMs let you “hot” swap mod-
ules in an operating IDU.
Front Panel
Signal and power connectors and service indicators mount to the chassis
front panel (Table 1-B). A green indicator lights when the unit is pow-
ered. Condition indicators light on major (red) and minor (yellow) alarm.
1 2 3 4 5 7 8 9 11
12 6 10
The IDU includes front-access slots for plug-in LIMs, which may be re-
moved or replaced with the IDU mounted and powered. The same IDU
chassis accommodates all data rates and RF frequencies.
Table 1-B Front-Panel Features
1 DC Power 3-pin Phoenix connector to -48 Vdc or optional
+24 Vdc power. Mates with plug P/N 3024080-03.
2 ODU 50-Ω N-type connector for signal and power
between IDU and ODU. 22dB cable loss at 270- or
350 MHz (300/400m of TM-LMR-500).
3 LEDs Power (green), Major Alarm (red), and Minor
Alarm (yellow) indications
4 Handset 4-pin RJ-11 connector for engineering orderwire
(EOW). Uses a DTMF handset that operates over
a 64-kbps auxiliary channel. If EOW is not used (or
if the handset is not plugged in) the channel is free
for use as a clear channel (see O/W1,O/W2).
5 COMPUTER 9-pin sub-D connector. 9600bps RS-232 serial
connection for radio management interface. Sup-
ports both text and GUI interfaces.
6 MODEM 9-pin D-type connector for RS-232 serial interface
to an external modem. Dial-up access to the IDU
IP management interface using a terminal applica-
tion such as HyperTerminal. The V.90 port
auto-senses modem signaling.
7 NMS 1/2 Two RJ45 ports for radio management interface
using internet protocol (IP). Ports provide bridged
IP interface to a 64-kbps channel for network man-
agement traffic. When connecting from a com-
puter to either port, or when cabling from the NMS
port of an IDU to the NMS port of another IDU, use
a crossover cable.
8 O/W1,O/W2 Two RJ-45 connectors for 64-kbps Service Chan-
nel. Used to bridge the EOW if installed. Without
EOW, OW1 becomes an across-the-hop 64-kbps
clear channel at RS422 levels, while OW2 and
handset disable.
For a current list of valid LIMs operate either separately with the second (right) bay covered, or in
LIM configurations use the combination as Table 1-D and Table 1-E list. The 10/100BaseT LIM op-
VALID command of the CLI.
erates in the left bay. The Proteus AMT radio can also accommodate
non-standard line combinations such as, mixed North American (DS)
and ITU (E) rates, DS rates over ETSI channels, and E rates over FCC
channels.
IDUs ship with mainboards matched with IF boards for an IF link at ei-
ther 60-MHz down and 270-MHz up, or an IF link at 140-MHz down
and 350-MHz up. DC power is either –48 or +24V.
IF bandpass filters reside on the IF board. Bandpass filters set the band-
width of the transmitted signal and provides adjacent channel rejection in
the receive path. The IF boards match radio bandwidth to radio capacity.
You can replace the IF board to change bandwidth. The IDU self-adjusts
to the new bandwidth. Changing bandwidth may affect the licensed spec-
trum of your radio; see Appendix F.
Outdoor 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 G describes The RFU mounts to the antenna with latches, so it can be replaced with-
alternate ODU mounting out using tools or affecting antenna alignment.
configuration - offset and
rack mounting. Table 1-G lists the basic RFU part numbers. Codes show the digits for
transmit/receive spacing, high/low (go/return) channel, and sub-band.
Appendix A lists these specific units.
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
Early model 7/8GHz The ODU uses 0.3, 0.6, and 0.8 meter, direct interface, high perfor-
radios interfaced antennas mance, low profile antennas for 13, 15, 18, 23, 26, 38-GHz radios. 1.2
through N-Type and 1.8-m high performance antennas are also available for 13, 15, 18,
connectors and flexible
waveguide. 23, an 26-GHz radios.
Appendix G describes Antennas include the radio interface flange (adapter) 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 secures the antenna to a tower or pole.
placement -
offset and rack mounting.
An RSU provides HSB The RSU also acts as the data connection point for 16E1/DS1 IDUs.
switching and 16 customer Since LIM size does not support 16 line connections, each 16E1/DS1
data connections. LIM requires an additional RSU to provide the customer line interface. A
RSUs do not bridge or 32E1/DS1 IDU would need two RSUs.
protect the engineering
orderwire. Jumper cables Switches match line types of the LIMs in the IDUs as listed below and as
link NMS and OW ports of Figure 1-11 and Figure 1-12 show.
co-located radios; see
Table 2-L. Table 1-I Redundancy Switche Units
Line I/O Connections
Offline IDUs on protected RSU Line Type
systems mute the OW port DB78 RJ48 BNC
to prevent echo problems 8/16E1 8209265-10 8209265-00
on ancillary equipment. 17-32E1 8209265-11 8209265-01
8/16E1/E3* 8209265-12 8209265-02
E3 / DS3* — — 8209265-03
2xE3 / DS3* — — 8209265-04
8/16DS1 8209265-15 8209265-05
17-32DS1* 8209265-16 8209265-06
8/16DS1/DS3* 8209265-17 8209265-07
*. BNC connections for E3/DS3 lines.
The RSU has automatic and manual modes. Normally, the switch re-
mains in the AUTO mode. With no alarms the switch logic initially sends
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. Transmitter and receiver paths switch together, but the far-end does
not switch.
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
the antenna. The transmitter of the path in standby gets attenuated by at
least 50 dB with a mute attenuator at the output of the transmit oscillator.
4/8/16E1
4/8/16DS1
E3
DS3
32E1
32DS1
1-16E1
17-32E1
4/8/16E1 + E3
4/8/16DS1 + DS3
Figure 1-11. Redundancy Switch Configurations with DB78 E1/DS1 Line Connector
4/8/16E1
4/8/16DS1
E3
DS3
2xE3
2xDS3
32E1
32DS1
4/8/16E1 + E3
4/8/16DS1 + DS3
Figure 1-12. Redundancy Switch Configurations with RJ48 E1/DS1 Line Connectors
The Redundancy Switch Unit (RSU) has common features on the left
side of the front panel, which Figure 1-13 shows. Table 1-J describes the
common features. The right side of the front panel includes a ground lug
for attaching ESD protection devices.
1 2 3
1 2 3 4 5
4 5
Figure 1-13. RSU Front Panel-Left Side
All versions of the RSU have connections for 100BaseT Ethernet data
from the IDU: LAN, LANA, and LANB. The RSU only switches one of
the 100BaseT IDU ports.
RSU line ports match RSU line ports (Figure 1-14) match those on the IDU. Figure 1-14 shows
those on the IDU. the RSU line connections. Chapter 2 details the pins of these connectors.
A high-density 100-pin connector interfaces line signals to 16E1 LIMs
on the IDU.
4/8/16E1 (DS1)
32 E1 (DS1)
E3 (DS3) / 2 x E3 (DS3)
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.
TXA
I N
IDU A
AUTO
IDU B
4 5 1 2 3
RSU to 100BaseT LIM
Two types of cable are available: standard cable for cable runs through
conduit, and plenum cable for cable runs in environmental air spaces
(plenum spaces). Plenum cables provide adequate fire-resistance and
have low smoke-producing characteristics.
cable_spectrum.vsd
Radio Management
All Proteus AMT radios include an out-of-band radio management chan-
nel for terminal-to-terminal communication of alarm, control, and status
information. This channel makes all operational data from both ends of a
link available at either terminal. A second overhead channel is a 64-kbps
Ethernet channel for SNMP radio management.
Each device controller accesses all alarms and controls in the IDU and
ODU. The controller also manages auxiliary output relays and external
TTL alarm inputs. Access the controller in several ways:
Element Manager
Element Manager (EM) is the Proteus AMT radio and radio network
maintenance and control system. EM gives radio installers, maintenance
personnel, and operators a tool for complete management and control of
their radios–on site or from remote locations–using the familiar Win-
dows environment.
EM Connections
EM queries the radio that you connect to, or address, for configuration,
events, and alarms, and then updates dynamic data every five seconds.
EM displays radio information, alarms, status, configuration, logs, and
reports. You can open any or all screens on the EM main window.
SNMP
SNMP Connection
Ethernet routing options include static routing – where you manually en-
ter up to 32 IP path addresses – or dynamic routing – where IP routing is
self-learning. Routing Information Protocol version 2 (RIP2) provides
dynamic routing of up to 15 radios in a subnet. Spans of these 15-radio
subnets are unlimited.
RIP is primarily for networks of moderate size and has these limitations:
After setting the IP address of the first-accessed radio locally, and then
configuring it as an intermediate gateway, routing tables of radios net-
work exchange and incorporate route information as the radio network
changes.
The management station, or SNMP manager, sends get and set requests
to the SNMP agents–the radios. The radio answers get and set requests
from the manager as specified by the MIB.
Each radio has two IP addresses: the Ethernet interface at the front panel
(LAN), 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 routing).
The text-based interface does not have the hardware and software re-
quirements of the graphical interface, and is small enough to be integral
to each radio – all you need is a terminal.
Telnet
Use Telnet to connect to the Proteus AMT radio via IP without using an
SNMP manager. Telnet is a terminal emulation program for TCP/IP net-
works. Telnet typically comes with Windows. Connecting to the radio
through Telnet enables the text-based interface – CTI/CLI.
The Telnet option enables commercially available TCP/IP network man-
agement facilities a method of monitoring Microwave Networks' Proteus
AMT radios.
To start a Telnet session, connect to the IP address of a radio on your net-
work, and then log in to the radio by entering a valid user name and pass-
word.
Telnet Connection
Specifications
Proteus AMT is a mixed Plesiochronous Digital Hierarchy (PDH) and
packet data radio. The radios service PDH lines that use international
digital (E-carrier) standards defined by the ITU-T, and that use North
American (T-carrier) digital transmission standards defined by ANSI.
The first few tables cover general radio specifications. Subsections that
follow list specifications for international and North American standards.
The index below lists the individual specification tables in this section.
Note: The last section of this chapter lists specifications for radios that
can service both T- & E-carrier signals.
The following tables list specifications for non-protected radios that use
the International (CEPT; E-carrier) digital transmission format. For a
hot-standby radio the branching loss is 1.9 dB on the main transmitter
and receiver and 6.5 dB on the standby transmitter and receiver.
Table 1-R lists transmit power for all data rates and bandwidths. Table 1-S
and Table 1-T list PDH specifications for 2E1 to 32E1\2E3. Table 1-U
through Table 1-Y lists 100BaseT specifications of valid 100BaseT con-
figurations at time of publication.
The last section in this chapter lists specifications for radios that service
both digital signal formats (T- & E-carrier).
The following tables list power and threshold measurements for non-pro-
tected radios using the North American (T-carrier) digital transmission
format. For a hot-standby radio the branching loss is 1.9-dB on the main
transmitter and receiver and 6.5-dB on the standby transmitter and re-
ceiver.
Table 1-Z lists transmit power for all data rates and bandwidths.Table 1-AA
to Table 1-AD list PDH specifications for 4DS1 to 2DS3. Table 1-AE
through Table 1-AL lists 100BaseT specifications of valid 100BaseT
configurations at time of publication. The section following lists specifi-
cations for radios that service both digital signal formats (T- & E-car-
rier).
Overview
This material covers This chapter outlines physical installation of the Proteus AMT radio. See
physical installation. Chapter 3, Commissioning, to setup the radio and start traffic.
See Chapter 3 to setup
and initialize. Proper installation planning includes: selecting a site, verifying ground-
ing, 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 RSU
• installing the ODU
Location
When selecting a site look for:
• Climate-controlled environment with adequate air flow for the IDU
• Ample power. When using an AC-to-DC supply consider that inrush
current can be ≥8A for up to 3 ms. MNI recommends its AC
converter, P/N 8708263-00. If used, rate circuit breakers to handle
initial in-rush current: ≥6A with trip characteristic 'C' or slower.
• Site ground that meets ITU-T Rec. K.27 and local standards
• Proper floor loading, space, and overhead support
• Enough clearance in front of the equipment for maintenance
• Enough lighting for installation and maintenance
Environment
Mount the IDU away from heat sources and in a weather–protected area.
The IDU chassis relies on convection to cool the boards. Keep heat sinks
on the back of the chassis clear of obstruction.
The ODU is exposed to severe weather. Ensure all RF Unit cover screws
are tight. Seal and weatherproof any external connector. Deterioration of
connectors from moisture can cause serious problems.
Grounding
Ideally, a grounding system provides the shortest possible path and the
lowest possible impedance to the ground reference point. The ground
reference is established by buried grids for telecommunication site-spe-
cific situations (tower and shelter) or the water pipe and/or buried ground
rods (usually at the power entry point) for a building.
The RSU has a RG48 line interface and a high density DB78 interface.
Pins of the DB78 connect the signal pair of each T1/E1 line. A DB78
mating connector, PN 3070037-0, comes with the RSU, but pre-fabri-
cated cables are available on request: DB78p-DB78p, PN 8108721-xx;
DB78p-16xRJ48, PN 8108722-xx; and DB78p-wire wrap, PN
8108723-xx (page 2-14).
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.
The cable between the computer and the hub must be less than 100
meters long.
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 should have a ground bar that runs down the front. This as-
sembly accepts up to 6-AWG stranded grounding wire. Attach this to the
office/building ground.
Unpack 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 labeled at the factory to match the ODU. MNI recommends
that you keep IDU and ODU pairs together, but IDUs work with any
ODU.
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. Do a preliminary installation of the ODU if
you are not sure.
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 cable loss at 270- or 350-MHz
(for 270-MHz about 300 meters/1000 feet of cable).
• 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 plastic
electrical insulating adhesive tape. Seal with a coat of sealing
compound.
– 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 or equivalent) with
male N-connectors at each end of the cable. The crimp tool and die that
Table 2-A 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.
Mount the IDU shelf in the standard 19-inch equipment rack or equip-
ment cabinet. The chassis occupies one rack space and does not require
forced convection cooling. When mounting:
A non-protected units takes one rack unit (1RU; 1.75 inch) of space, and
the protected radio units take from 3- to 4 RUs depending on capacity;
two RUs for the IDUs and 1 or 2 RUs for a redundancy switch unit
(RSU).
Ground the IDU to facility The IDU chassis must be grounded to the facility grounding system to
ground to prevent damage minimize the likelihood of damage from lightning strikes and the impact
to equipment and ensure of electromagnetic- and radio frequency-interference (EMI/RFI).
reliable operation. Grounding systems for towers and shelters that follow published guide-
lines, such as ITU-T Recommendation K.27, provide the ground refer-
ence necessary for reliable radio operation.
The IDU chassis has points for grounding to an appropriate ground.
Connect Power
Plan power circuits for The connector to the front panel is a 3-pin Phoenix, P/N 3024078-03.
in-rush current ≥8A up The mating plug, P/N 3024080-03, ships with the IDU. To connect
to 3 ms. power:
NOTE: The radio does not work without proper ground connections.
If used, rate circuit Both the -48V and +24V power supplies require a ground reference in
breakers to handle the order for them to turn on. Mounting screws ground a unit that you mount
in-rush current: ≥6A in a grounded EIA rack or enclosed cabinet. Otherwise, you must con-
with trip characteristic nect "ground" (pin 3) to the facility ground.
'C' or slower.
Ground '+' of the 48V supply to 2. Turn your power supply on and check the polarity of the supply leads,
set ground reference. and then turn your power supply off.
Ground '-' of the 24V supply 3. Connect positive supply lead to the positive pin of the mating plug as
to set ground reference. 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.
DC input to the 48V power supply will be between -40 to -60 Vdc (nom-
inally -48V). The power supply tolerates up to 1Vpp input ripple, DC to
50 MHz, such that the peak voltages stay within the -40 to -60V limit.
NOTE: While the -48V power supply accepts from -40 to -60V, there
will be up to 100 mV drop between the IDU input connector and
the ODU connector. Under worse case conditions, voltage to the
ODU varies from -39.9V to -60V
DC input to the 24V power supply will be between +19 to +30 Vdc
(nominally +24V). The power supply tolerates up to 1Vpp input ripple,
DC to 50 MHz, such that the peak voltages stay within the +19V to
+30V limit.
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.
Use a source that can Plan power protection devices, such as fuse panels, breakers, and un-in-
handle an in-rush current terruptible power supplies (UPS), to account for the IDU power protec-
≥8A up to 3 ms. tion and to handle an 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 protec-
tion devices.
6A SLO-BLO
Battery IDU
Pack
48V/24V If using a breaker,
use ≥6A trip rating 'C'
or slower.
AC Pow er Connection Must handle
8708263-00
Converter is internally limited; inrush current;
no fuse or breaker needed. ≥8A for 3ms.
AC PWR
48V
UPS AC/DC IDU
Line input and output connect to LIM ports on the non-protected radio.
Transmit (TX) signals flow Data signals (Table 2-C) connect via RJ48 wiring using twisted pair ca-
to the IDU (to the RF ble to connectors on the LIM; DS1 signals use 100-Ω connectors.
transmitter). E3/DS3 signals (Table 2-D) connect to 75-Ω unbalanced BNCs.
10/100BaseT signals (Table 2-E) connect via RJ45 wiring on UTP
Receive (RX) signals flow CAT5 cable to 100-Ω balanced connectors. 16E1/DS1 signals connect
from the IDU (from the RF through a 100-pin high density connector to a jumper cable that carries
receiver). signals to a redundancy switch unit (RSU) for customer access. The RSU
acts as the line signal cabling point. A 32E1/DS1 needs two RSUs.
The RSU of the hot-standby protected radio splits line inputs and sends
them to both IDUs on the transmit side of the radio. The RSU switches
line output from the online IDU to the output connector(s) on the receive
side of the radio. Line input and output connects to the line connectors on
the RSU. The RSU provides either 120-Ω balanced RJ48 line connectors
or a DB78 high-density line connector (Table 2-F) for E1 line signals;
100-Ω for DS1 signals.
The 16E1/HSBY LIM has a 100-pin high density connector that brings
data signals to the front panel. Data from a 16E1/DS1 LIMs are typically
bridged to an RSU that acts as the distribution box. LIM and connector
size prohibits direct connection. Table 2-H lists the cable pinning for the
16E1/DS1 LIM high-density connector for customers who prefer to use
their own distribution method.
Figure 2-4 shows a non-protected 32E1–DS1 system with the DB78 ver-
sion of the RSU. A DB78 mating connector, PN 3070037-05, comes
with the RSU. Pre-fabricated cables are available on customer request;
see "Cable and Connector Considerations," on page 2-2.
IDU
RSU
CH1-16
RSU
CH17-32
3700050-00
DATA I/O ribbon cable set
Figure 2-4. 32E1/DS1 NP Configuration; Line Signal on DB78
Use the twisted pair sets of Table 2-F DB78 Line Signal Connector Wiring
your cable for each ring/tip Female front
signal of E1/DS1 lines. panel connector
shown; mating
Do not untwist any pair connector pins
more than 12.7 mm (1/2 are the mirror
inch). image
Use the RJ48 wire list in Table 2-C to build individual RJ48 line cables.
Figure 2-6 shows a non-protected 32E1/DS1 system with the RJ48 ver-
sion of the RSU.
Table 2-H provides a wire list of the 100-pin high density connector and
cabling from the 16E1 LIMs for troubleshooting and maintenance. The
cables come with the hot-standby system.
Radio service channels provide the path for radio performance data and
alarm messages, and for issuing configuration and control statements to
individual radios, radio hops, and multiple radios of a radio network.
This overhead channel includes the network management channel for ra-
dio management communications and the auxiliary channels that the
next section covers.
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:
• MODEM: 9-pin D-type connector for RS-232 serial interface to an
external modem. A 'dialer/monitor' feature negotiates the telephone
signaling to establish the dial-up serial link. Access the connection
using a communication application such as HyperTerminal.
• COMPUTER: 9-pin sub-D connector. RS-232 serial interface to
computer using VT100 emulation at 9600 bps.
• NMS: two RJ-45 ports for Ethernet access to radio management data.
Ports are bridged networks. Access the radio using SNMP or an
Ethernet application such as Telnet.
The following tables detail these connections.
A modem connects as a Table 2-I Modem Connection (IP Interface; Sub-D 9-Pin Male)
terminal (DTE) device. The Pin Signal Direction
connection between IDU
1 CD Modem-->PC
and modem is a straight
through RS-232 cable. 2 RXD Modem-->PC
3 TXD PC-->Modem
4 DTR PC-->Modem A cable connecting a DTE
5 GND Modem-->PC to DCE wires straight
6 DSR Modem-->PC through.
7 RTS PC-->Modem
8 CTS Modem-->PC
9 RI Modem-->PC
Wire the COMPUTER port Table 2-J Computer Port* (Serial; Sub-D 9-Pin Female)
serial cable straight Pin Signal I/O
through. 1 NC
2 TXD O
3 RXD I
4 NC
5 GND
6 NC
7 NC
8 NC
9 NC
* Wire the serial cable straight-through.
Top NMS port is primary; Table 2-K NMS Connection* (IP Interface)
bottom the repeater. 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. Jumper
cables, P/N 8109726-00, are available for NMS bridging.
Configure RS232 AUX Configure the two RS232 channel baud rate, parity, stop bits, and polar-
channels and map alarms ity using the radio management applications–CTI or EM.
to relays using the radio
management applications– Relay alarm outputs are available on four Form-C relays. Four alarms are
CTI or EM. mapped to the output relays. Alarm relay default settings are: 1-NE MA-
JOR SUMMARY, 2-NE MINOR SUMMARY, 3-FE TERMINAL FAIL-MINOR,
4-TERMINAL-TO-TERMINAL CHANNEL FAIL-MINOR. Edit the alarm map
table using CTI or EM.
I N
IDU A
AUTO
IDU B
4 5 1 2 3
RSU to 100BaseT LIM
The RSU currently provides All versions of the RSU have LAN connections for 100BaseT applica-
switch protection for one tions. The RSU has three RJ45 connectors: one for customer input (LAN),
100BaseT port. one for connection to the main radio LIM (LAN A), and one for connec-
tion to the standby radio LIM (LAN B). Although a 100BaseT LIM has
four ports, the current RSU provides one switch-protected path. Connect
a 100BaseT LIM port to the RSU using either a straight-through or a
twisted pair cable. Table 2-P list straight-through wiring, and Table 2-O
lists the cross-over cable and wiring.
Table 2-P 100-BaseT Cabling Between IDU and RSU
IDU RSU
Pin Signal Pin Signal
LAN A LAN
1 Rx + 1 Tx +
2 Rx – 2 TX –
3 Tx + 3 Rx +
4 GND 8 1 4 GND
5 GND 5 GND
6 TX – 6 Rx –
7 GND 7 GND LAN B PROG
8 GND 8 GND
type and the customer and system line connections for RJ48 and DB78
versions.
After physically installing the RSU and IDU see Chapter 3 for commis-
sioning the radio.
• 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
Table 2-Q 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.
Unpack Hardware
Carefully unpack the antenna assembly and mount from its shipping car-
ton. The standard 0.3- and 0.6-meter (1- and 2-ft.) antennas ship partially
assembled and include the following components:
• reflector and radome assemblies
• feed assembly
• offset tower mount
• various bolts, nuts, flat washers, lock washers, allen keys
• tube of Loctite
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 early-model RF The antenna has a feed assembly that couples the non-protected RF unit
interface on 7/8-GHz units directly to the antenna. Install the RF unit after properly installing the an-
was Type-N connectors and tenna feed o-ring.
a short cable assembly.
Current units are press-fit. 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.
See the next subsection A hot-standby ODU has two RF units mounted on a coupler / mounting
installation of early-model assembly. The coupler connects to the antenna like the non-protected RF
for 7/8-GHz ODUs. unit. Snap fasteners hold the assembly in place and four socket-head
screws secure it to the back of the antenna
Hot-standby couplers have antenna interface adapters that set polariza-
tion. The coupler ships with polarization set as you order, and the alter-
nate polarization adapter ships in the same package as the hot-standby
RF unit assembly.
Overview
This chapter outlines procedures to align and setup the Proteus AMT ra-
dio for operation after physical installation; see Chapter 2 Installation.
Use this material to configure your radio and start traffic as soon as pos-
sible.
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-3) detail.
Turn on power to the IDU. If nothing happens, verify the supply voltage
at the connector with a voltmeter.
Under normal conditions the green 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 customer traffic.
System – shows and lets you set date and times, radio name, location,
and contact information.
ODU – shows and lets you set the transmit frequency and output power,
ATPC and the RSL set points, and has an ODU Mute control.
IDU – displays and lets you configure orderwire and auxiliary channels.
LIM – shows the installed LIM and lists valid types. Lets you configure
a LIM to a valid type other than the installed type.
IP Address – view or set IP addresses and network masks of: LAN (ra-
dio), WAN (IPO-Air), or TFTP server for code download. Also, set trap
mode to silent–off, verbose–all data, or terse–summary. Default gateway
lets you define where the radio sends IP packets destined for other IP
subnets.
This procedure should have been done after ODU installation, however
this section repeats the steps for convenience.
2. Pan the ODU in azimuth using the fine azimuth adjustment to locate the
main lobe of the microwave signal. Watching the AGC voltage at the
receive site for peak signal. The main lobe will have the highest
AGC voltage. RSL at the IDU should be close to the figure
determined in your path calculation.
As Figure 3-1 shows the signal side lobes are typically 15-20 dB
down. If the signal peaks below the expected level, you most likely
are on a side lobe or have cross polarized the antenna. There are
sharp drops in power response between the lobes and broad response
at the peaks.
3. After locating the main lobe stop panning at the point of maximum
signal strength (highest AGC voltage).
4. Tighten azimuth adjustment nuts just enough to prevent the ODU from
moving.
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.
The RSL display only reads If the level is lower than predicted, identify and fix the discrepancy.
up to -90 dBm, and does not These include: checking the path for line-of-sight and proper fresnel
accurately measure RSL for clearances, recalculating the path parameters and checking transmit
radios operating beyond power. Also, verify antenna polarization and alignment.
-90 dBm.
Normally, each radio ships fully configured. Outdoor units are set and
tested at the frequencies that each customer orders. If a link requires
changes to ODU operating frequency use element manager, or craft ter-
minal interface, from the local access port to change settings. Configura-
tion changes require administrative-level access.
Set Capacity
The radio auto-senses capacity based on the line interface modules
(LIMs) you plug in to the indoor unit (IDU).
The IDU has combinations of LIMs that allows the system capacity to
operate within set bandwidths. See Chapter 1, Table 1-D and Table 1-E
for valid configurations.
The IF board matches radio bandwidth to radio capacity: 3.5, 7, 14, and
28-MHz bandwidth for ITU channel plans, and 5, 10, 20, 25 MHz for
FCC channel plans. Change the IF board to increase capacity beyond
bandwidth limits.
Set Tributaries
To set LIM line types in EM or CTI:
1. Open Configuration from the main menu
2. Select LIMA/B
3. Configure your proposed LIM type for both near- and far-end LIMs, and
primary and secondary LIMs on hot-standby radios.
For example, the IDU reads that an 8E1 LIM is the 'installed type', but
you may want to temporarily use the LIM as a 4E1; your 'proposed type.
4. In EM click Apply to set changes and continue working
Use can also vary the data 5. Select Equipped to allow the IDU to monitor the channel for loss of
rate of 100BaseT LIMs in signal. Unequipped channels pass traffic unmonitored
the 'A' slot on a 2 x 100BT
radio. The data rate of LIM 6. In EM click Apply to set changes and continue working, or click OK to
'B' adjusts accordingly. set changes and exit
Overview
This chapter focuses on operation in the transmit direction since receive
functions are reverse. The chapter also covers protection switching and
network management.
Basic Operation
The Proteus AMT radio connects distant points in a communication net-
work by converting input data to a radio frequency (RF) signal that can
be carried at microwave frequencies. As 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
The IDU converts line data and radio overhead channels to and from an
intermediate frequency (IF) for conversion by the ODU. This transport
function is bi-directional; that is, it separates into transmit and receive
functions.
A single coaxial cable provides the path for IF signals between the IDU
and ODU. The cable also transfers radio telemetry signals and power to
the ODU.
As Figure 4-2 shows, signal flow in the transmit direction includes signal
conditioning, multiplexing, modulation and correction coding, and then
conversion to an 270- or 350-MHz intermediate frequency. The ODU
then converts the IF to a radio frequency (RF) signal for transmission
across the microwave link. Operation is full-duplex; that is, the radio
transmits data in two directions simultaneously.
IDU
LIM-A ODU
Multiplex Coding
IF RF
and and
Processing Processing
Frame Modem
LIM-B
Line Interface
Line
Transformers Interface
n
Rx FIFO-n
Tx Bus To Mainboard
Line Connectors
Rx Bus
Tx FIFO-0
Line
Transformers Interface
0
Rx FIFO-0
Figure 4-4 shows the multiplexing and modulation functions of the IDU
detailed in the following sections
.
Modulate
RS Trellis Preamble
MUX Scramble Interleave & Pulse DAC
Encode Encode Insert
Shape
Signal Multiplexing
The multiplexer, Figure 4-5, 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 Tx FIFO
empties before the allocated frame slot fills, the LIM breaks the
valid-data signal and the multiplexer inserts stuff-data. For the Rx direc-
tion, the multiplexer discards stuff-data and parity words from the
far-end are not written to the Rx FIFO.
Transport
Channels
LIM-A
LIM-B Rx Bus
Service Multiplex
Channels
Aux1 Tx Bus
Overhead Channel Interface
Aux2
HS
OW1 Orderwire
OW2
Management
Channels
Term-term
IPOA
Data from the overhead channels (service and management channels) get
multiplexed into the radio link in the same fashion by the mainboard via
the overhead channel interface as Figure 4-6 shows.
Service channels are provided for the network provider and can be turned
on or off. The radio management channels provides the terminal-to-ter-
minal communications, such as commands and status, and are always on.
LIM-A
LIM-B Rx Bus
Service Multiplex
Channels
Aux1 Tx Bus
HS
OW 1 Orderwire
OW 2
Management
Channels
Term-term
IPOA
Service Channels
The IDU carries auxiliary data and orderwire channels. Two auxiliary in-
terfaces correspond to the two RS232 auxiliary radio channels. Three or-
derwire interfaces – handset, OW1/OW2 – go to one orderwire channel.
The RS232 AUX1 and AUX2 data channels can be independently set for
9.6 or 19.2 kbps; odd, even, or no parity; one or two stop bits; and in-
verted or non-inverted polarity.
Orderwire provides three local interfaces: handset, OW1, and OW2, and
one radio-link interface for transporting an 8-bit, 8k-sample, mu-law
voice channel. The orderwire operates in either voice or data mode.
Offline IDUs on protected In voice mode, the radio transmits data from only one of the local inter-
systems mute the OW port faces at a time based on activity. The channel that is “loudest” seizes the
to prevent echo problems channel. Orderwire is carried over the radio link as a 64 kbps channel.
on ancillary equipment.
Each front-panel interface (Handset, OW1, and OW2) receives the
“loudest” of the three remaining interfaces (the two other front-panel in-
terfaces and the received over-the-air channel). OW1 and OW2 each
have data rates of 80 kbps that convert to 8 kilobytes per second.
Assign each IDU a unique station number using EM or the text-based in-
terface. An integral decoder recognizes the station number and activates
the IDU buzzer to indicate when the IDU is called.
IDU IDU
OW1 OW1
OW2 OW2
HS HS
IDU IDU
OW1 OW1
HS OW2 HS OW2
Management Channels
The radio carries two management channels over the link: a 64 kbps
IP-over-the-air (IPO-Air); IP over TCP/IP channel and a non-IP termi-
nal-to-terminal channel at 9.6 kbps.
The terminal-to-terminal channel operates even if the TCP/IP stack or
other higher-layer services are unavailable.
overhead channel get transported in the order read from the LIMs and
overhead channels.
Stuff slots let the radio link and line interfaces transmit asynchronously
–intermittently rather than in a steady stream. A data unit that represents
the stuff counts of each LIM or overhead channel as well as frame stuff
counts get inserted into the frame. Stuff counts and redundancy checks
are used to detect frame transmission errors.
Aggregate loopback is a digital loop of the modem. Input from the line
interface and multiplexer connect to the demultiplexer for output to the
LIM tributaries.
-48 Vdc powers the ODU. The ASK telemetry path has a combined pass
band of 2- to 20 MHz. Uplink telemetry is 5.5 MHz and downlink telem-
etry is 10 MHz. 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 270- or 350 MHz transmit IF and 60-
or 140 MHz receive IF. Total insertion loss for the 60 MHz IF is 5 dB,
and for the 270 MHz IF path 97 dB.
The board gets the nominal 60 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 60 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.
RF Conversion
DC, IF, and telemetry signals go to the RF unit at the ODU through the
IDU-to-ODU coax cable. The multiplexer separates signals from the
IDU and combines signals to the IDU. -48 Vdc from the IDU powers the
ODU. The unit double up-converts the transmit IF to the output RF and
double down-converts RF to the receive IF.
As Figure 4-8 shows, the main-board in the RF-unit performs IF/RF con-
version and local oscillator functions. The transmitter, receiver, and di-
plexer provide the proper operating frequencies.
TRANSMITTER PA
MAIN BOARD
LO2 DIPLEXER
MUX LO1 TX OSC. ANTENNA
IDU
TX/RX
OSC.
LO2
RX OSC.
RECEIVER
Protection Switching
The Proteus AMT radio has a hot-standby (HSB) configuration for redun-
dancy protection. In this configuration the radio has two terminals (IDU
and ODU) connected to a Redundancy Switch Unit (RSU). The RSU
provides switching for the transmit and receive signal paths should one
of the radios develop a problem. The RSU selects the best path by moni-
toring the alarm status of both IDUs. Transmit and receive paths switch
together.
ID U
(M AIN )
CONTROL
D AT A
& S T AT U S
ODU
USER (M AIN )
D AT A HOT
S T AN D B Y CO UPLER
S W IT C H
ODU
(S T AN D B Y )
CONTROL
D AT A
& S T AT U S
ID U
(S T AN D B Y )
H S B _O P .V S D
Both radios operate at the same frequency. The main radio transmit path
connects via the through-arm of a coupler while the standby radio con-
nects via the coupled arm. Transmit power is 7-dB lower than a non-pro-
tected radio on the standby path and 1-dB lower on the main path.
On the receive side, the signal from the antenna goes through the same
coupler as the transmitter. At the receive side of the IDU, a relay
switches data from the online IDU to the customer output connector(s).
Switching logic controls the relay.
The receive splits in the RF coupler. Receive threshold on the standby re-
ceive path is about 7-dB worse than on a non-protected radio, and 1-dB
worse on the main path. But, a properly planned path it is adequate for all
but the worst conditions. Normally the system operates only on the pri-
mary receivers and switches to standby on hardware failure.
Table 4-A Typical Hot-Standby Switching Time
IF BW Manual Software Loss of Signal High IDU Power ODU Power
Switch (Online Request) (Data Input) BER Fail Fail
28 MHz 281.3 ms 289.1 ms 318.1 ms 432.2 ms 309.1 ms 221.3 ms
14 MHz 175.4 ms 161.2 ms 175.4 ms 281.9 ms 190.8 ms 159.2 ms
7 MHz 164.2 ms 170.3 ms 196.0 ms 190.6 ms 190.6 ms 181.7 ms
3.5 MHz 313.8 ms 374.4 ms 361.4 ms 162.2 ms 162.0 ms 186.7 ms
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)
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 radio as Figure 4-11 shows. Radio interfaces connect open-system
and proprietary management software to the radio. Software includes a
command line interface (CLI), a text-based menu system called the craft
terminal interface (CTI), and the graphical system called Element Man-
ager (EM).
FRONT PANEL
RADIO MANAGEMENT
NMS/SNMP-1 CHANNELS
ENET ENET
ENET
Repeater Driver
NMS/SNMP-2 IPOA Ch
HDLC SERIAL
Driver (64 kbps)
DIALER/
IP
MONITOR
SERIAL
MODEM/PPP UART PPP
Driver
TCP/UDP
RADIO API
SNMP
Near End Data
TELNET CLI
Term-Term SERIAL Term-Term Ch
COMPUTER Protocol Driver (9.6 kbps)
SERIAL
CLI/CTI UART Driver CLI
Far End Data
The craft terminal interface (CTI) is a serial craft interface for local radio
management at 9600 bps. The local COMPUTER port does not use the
SNMP agent or the TCP/IP stack, but 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-12 outlines the CTI/CLI management
software menus and choices and Figure 4-13 outline the EM menus and
selections.
Page 4-12
Operation
Connect NE/FE Alarms RF Statistics Inventory ODU Mute IDU Copy Image Files
NE/FE Tx Power Image Booted TX control and timer Radio name & location primary to secondary
Disconnect NE/FE Test display of min/max/avg. NE/FEODU Contacts secondary to primary
Page 4-13
User Interfaces
Operation
Overview
Proteus AMT radios require minimal preventive and corrective mainte-
nance. Checking terminal and link performance periodically and analyz-
ing the performance logs uncover problems that may need attention.
Telephone Support
Include the RA number both 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
Replacing LIMs
Each IDU accepts up to two line interface modules (LIMs). The two
LIMs can be installed in any combination up to the maximum data rate
compatible with the system bandwidth as “Line Interface Modules” on
Page 1-6 describes.
You can hot-swap LIMs, that is, remove of replace a LIM while the sys-
tem is powered without interrupting traffic on the other. After installing a
LIM, the IDU determines the LIM type but does not automatically
change tributary configuration. The active and enabled tributaries would
operate until you make changes.
Of course, system gain decreases at the higher data rates, but if the path
was planned for eventual capacity upgrade, the reduced gain will be suf-
ficient for a reliable hop.
5. Install the new LIM. Seat and secure using the two retaining screws.
The cartridge fuses listed below are part of the power supply protection
from severe lightning strikes and against shorting. The fuse opens only in
the case of an excessive surge, a component failure, or a short on the ca-
ble to the 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 power supply mounts on the left side of the chassis. To replace the
power supply:
Replacing IF Boards
IF boards have an EMI/RFI The radio ships with a fixed occupied bandwidth of: 3.5, 5, 7, 10, 14, 20,
cover. Some figures here 25, 28, or 30 MHz. Changing occupied bandwidth requires replacing the
show the cover removed. IDU IF board. Figure 5-1 shows the location of the board in the IDU
chassis.
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 latches. So, any RF unit can be removed
from the antenna without changing antenna alignment.
Other than the antenna fitting, the head 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 head 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.
Updating Firmware
Get a free trial version of a Download firmware from through the front panel Ethernet NMS port us-
TFTP server at ing any networked PC running TFTP server software. Configure the
http://www.solarwinds.net TFTP according to the product instructions.
NOTE: Firmware files are available on the CD that ships with your
system. You can also download updates from our web site at
www.microwavenetworks.com.
Get a free trial version of a Download firmware from the Ethernet NMS port using any networked
TFTP server at PC running TFTP server software.
http://www.solarwinds.net
Download Files and Reboot Radio
1. Log in to IDU
2. From main menu, select 5-Utilities
3. Select 1-Download Files
4. Select a radio to update – NE/FE primary or secondary (protected)
5. Select 2-Flash Destination
6. Select code type – bootloader, application, IDU Tx\Rx, or LIM
7. Select 3-TFTP File Name
8. Enter the download file name
9. Select 5-TFTP Server Address
10. Enter the IP address of your TFTP server
11. Select 1-Begin Download
Maintenance Checks
Periodic Maintenance
The Proteus AMT Radio requires only periodic inspections to isolate po-
tential problems and ensure trouble-free operation.
Monthly Checks
Use one of the user interfaces to check performance and event logs. Con-
tinued analysis of the logs over time give a good general indication of ra-
dio performance.
The RSL display only reads 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, oper-
ate 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.
Early model RF unit synthesizers had tuning ranges that were less than
the half-band of its frequency plan. Current RF units include wideband
synthesizers that cover the entire half-band of the frequency plan. How-
ever, the tuning range of any RF unit is the range of its diplexer. Tuning
past the diplexer range requires replacing the diplexer. Diplexer replace-
ment is a factory-level procedure; contact Customer Service for more in-
formation.
This section includes the following frequencies and channel plans that
Table A-A, on page A-2, lists.
18GHz, 60/270-MHz IF
15GHz, 60/270-MHz IF
13GHz, 60/270-MHz IF
7GHz, 60/270-MHz IF
7GHz, 140/350-MHz IF
8GHz, 140/350-MHz IF
13GHz, 140/350-MHz IF
13-GHz ODUs at 140/350-MHz IF have either rectangular (standard) or
circular (optional) antenna interface. The antennas you purchase must
matched this interface.
Table A-X 13GHz 266 MHz T/R Spacing; 140/350-MHz IF
Sub- ODU P/N ODU P/N TX Lower TX Upper RX Lower RX Upper
Band Rect. Interface Circ. Interface Limit, MHz Limit, MHz Limit, MHz Limit, MHz
LB1 63-130266-00111-6100 63-130266-00111-6100 12751 12814 13017 13080
HB1 63-130266-10111-6100 63-130266-10111-6100 13017 13080 12751 12814
LB2 63-130266-00211-6100 63-130266-00211-6100 12807 12870 13073 13136
HB2 63-130266-10211-6100 63-130266-10211-6100 13073 13136 12807 12870
LB3 63-130266-00311-6100 63-130266-00311-6100 12863 12926 13129 13192
HB3 63-130266-10311-6100 63-130266-10311-6100 13129 13192 12863 12926
LB4 63-130266-00411-6100 63-130266-00411-6100 12919 12982 13185 13248
HB4 63-130266-10411-6100 63-130266-10411-6100 13185 13248 12919 12982
*LB-LOW BAND; HB-HIGH BAND
15GHz, 140/350-MHz IF
18GHz, 140/350-MHz IF
23GHz, 140/350-MHz IF
Aggregate Local Loopback Aggregate local loopback is active (minor). A digital loopback between
MODEM and LIM.
Aggregate Transmit PN Pattern Modem is transmitting BER psuedo-random number pattern instead of
payload data.
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 (mi-
nor).
Configuration Fail Modem did not configure properly due to LIM failure, equipment mis-
match, or modem failure (major).
Configuration Not Supported Current proposed LIM types indicate an invalid configuration (minor).
Custom BER Level Current BER is greater than the threshold specified by the alarm. The de-
fault value for the threshold is 10-9, but can be changed via alarm map-
ping (minor).
DTMF Buzzer The DTMF buzzer is currently ringing. This alarm can be mapped to a
relay, and the relay attached to an external buzzer or speaker for better
audio performance in high noise environments.
Far End Terminal Failure Far end IDU has a current major alarm (minor at Near-End terminal).
Flash Fail Power-up tests indicated that the FLASH failed (minor).
HotStandby Hi Priority Alarm Signals that one of the alarms that is mapped as an HPA (high priority
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.
HotStandby 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.
HotStandby Online Status Also called the On-line Command. Signals from Redundancy Switch
unit (RSU) to primary and secondary IDUs. The online radio receives a
signal that indicates that it is online, while the offline radio gets an offline
signal. Element Manager shows PROTECTION STATE on the Configura-
tion, Hot Standby screen. CTI menus show ONLINE COMMAND on the
Configuration, Hot Standby, Status screen. This is a status signal that is
not treated as an alarm; it indicates radio operational state.
HotStandby Other Radio Alarm An alarm used on the hot-standby radio configuration. The alternate ra-
dio has a high priority alarm (minor).
I2C Failure I2C bus (to IF board, PS board, and LIMS) failed.
IF Board PLL Lock Synthesizer on the IF board will not lock. Data will likely not pass over
IF (major).
LIM A/B Trib n Remote Lpbk Indicated tributary is in remote loopback (minor).
LIM A/B Trib n TX PN Pattern Indicated tributary is transmitting a BER psuedo-random number pattern
(minor).
LIM A/B Trib. n (1–16) RX AIS AIS (blue signal) received on n (1–16) tributary.
Minor Alarm Summary Any alarm condition that degrades radio performance or a radio in diag-
nostic 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).
Primary Power Supply Fail Power supply of main unit is in alarm. Problem will likely kill the pro-
cessor before the alarm turns on (major).
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 mapping (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 Fail Power supply of Redundancy Switch Unit is in alarm (major).
SRAM Fail Power-up test indicated that the SRAM failed (minor).
Term.-to-Term. Chan. 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 (unexpected
reset; major).
Overview
A controller in the IDU handles radio operation by accessing all alarms
and controls in the IDU and ODU. The controller also manages auxiliary
output relays and external TTL input alarms. Users have three manage-
ment interfaces to the controller through the front-panel management
ports that Figure C-1 shows: Element Manager – the Windows™ graph-
ical user interface, CTI – the text-based menu interface, and SNMP – an
industry standard IP interface. The front-panel management ports in-
clude:
• COMPUTER–local RS232 serial connection
• MODEM–serial connection using point-to-point protocol
• NMS–RJ45 Ethernet interface for SNMP
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
The computer port on the IDU front panel provides direct RS-232 serial
access to radio maintenance applications at 9600 bps. Connect a VT100
terminal or use any terminal emulation program, such as the HyperTer-
minal program that ships with Windows™, to access the text-based
maintenance application.
Use Element Manager (EM) from a computer serial connection to the
front-panel computer port. EM asks for connection type on opening.
Set terminal emulation programs to VT100 compatible with the port set
for 9600 bps, 8data bits, noparity, 1stop bit, and xon\xoff flowcontrol.
NMS-SNMP
Proteus AMT radios have two RJ45 ports for 10BaseT Ethernet to an
SNMP (Simple Network Management Protocol) agent.
Access any radio from an Ethernet LAN or WAN using the radio IP ad-
dress. Once connected, use EM, Telnet, or any SNMP management soft-
ware to access radio configuration, diagnostic, or performance data.
SNMP Basics
SNMP provides open-standard radio management via Ethernet. Since
SNMP is an open-standard protocol, any SNMP-capable management
application may be used to manage SNMP-based radios.
RIP is primarily for networks of moderate size and has these limitations:
• Limited to sub-networks whose longest path is 7 hops (15 radios).
• Uses fixed metrics to compare alternative routes; so it is unsuited to
situations where routes need to be chosen based on real-time
parameters such a measured delay, reliability, or load.
After setting the IP address of the first-accessed radio locally, and then
configuring it as an intermediate gateway, routing tables of radios net-
work exchange and incorporate route information as the radio network
changes.
The management station, or SNMP manager, sends get and set requests
to the SNMP agents–the radios. The radio answers get and set requests
from the manager as specified by the MIB.
Each radio has two IP addresses: one addresses the Ethernet interface
(LAN), and the other the over-the-air interface (WAN). The over-the-air
interface transports radio support data, including get and set requests
from the SNMP manager, over the microwave link and to other ad-
dressed radios as routing tables define.
MIB Tables
Figure C-2 shows the major Proteus AMT SNMP objects.
Status–view link or radio status.
Performance–monitor radio
performance statistics.
MODEM
Because dial-up access uses normal telephone lines, the quality of the
connection is not always good and your data rates may be limited.
Connect and power a Configure a radio for dial-up access by connecting a modem between the
modem for PPP before phone line and the radio modem port. Set the modem to Auto-Answer.
powering the IDU. The IDU does not have dial-out capability.
If a connected modem The default modem initialization string (AT&F0) is not required for PPP
resets, reboot the radio to connection. A different value or no value (0) will not affect operation.
re-establish PPP
communication. You must connect and power a modem to the PPP modem port and re-
start (or re-boot) the IDU for a PPP session to work. This is not a
plug-and-play connection. And, if the connected modem breaks the con-
nection
2. PPP IP has to be valid when the radio boots up, if it is set to 0.0.0.0
PPP won’t work. Problem Fixed.
Element Manager
Element Manager® (EM) is the 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
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. A guest can view, but not
change, radio parameters. An Administrator can make changes to the ra-
dio configuration. Your password logs you into both the local and remote
radios at the same security 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 an adminis-
CONFIGURATION trator save the radio setup to a configura-
command opens a restore tion file (.cfg) that you can reload, or load
options box. The RESTORE to another, replacement, radio.
PASSWORDS option is
Restore Configuration lets an adminis-
typically not used. The
trator load a specific radio configuration
option restores
file.
passwords that you
manually edit in your You can load configuration files in Demo
backup file. If not mode for validation and troubleshooting.
manually entered, EM Alarms and Test Settings displays are
sets passwords as three identical for near- and far-end radios, and
asterisks (***). 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 margin,
and AGC voltages of the near-end/
far-end, and primary/secondary receivers.
Min, Max, and average RSL displays in
RF Statistics.
G.826 Statistics shows link error perfor-
mance statistics.
Use History to configure and display his-
torical performance data.
You can save performance data to a
comma-separated values (.csv) file man-
ually or automatically, and import these
files into database or spreadsheet appli-
cations 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. Performance and BER data, however,
refresh in 5-second intervals and not in a continuous real-time mode as in
the Element Manager (EM).
Data on CTI screens does The boot code is the first software loaded during power-up or IDU ini-
not refresh in real time. 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 the link operational.
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
NewRadio-99, Major Alarm, Link Down >
Alarm Menu
--------------------------------------------------
Alarm Menu
1. Current Alarms
2. Latched Alarms
3. Alarm Log
4. Change Log
5. Clear All Latched Alarms
0. Exit
NewRadio-99, Major Alarm, Link Down >
Performance Menu
--------------------------------------------------
Performance
1. Near End Primary
2. Far End Primary
3. Near End Secondary (Local)
4. Far End Secondary
5. Reset All Stats
0. Exit
NewRadio-99, Major Alarm, Link Down >
Test Menu
--------------------------------------------------
Test Menu
1. Aggregate Local Loopback
2. Aggregate BER Test
3. Tributary Loopback
4. Tributary BER Test
5. ODU Mute
0. Exit
NewRadio-99, Major Alarm, Link Down >
Configuration Menu
--------------------------------------------------
Configuration Menu
1. IDU
2. ODU
3. LIMs / Modulation
4. Service Channels
5. Hot Standby
6. IP
7. Alarms
8. Reset to factory Settings
0. Exit
NewRadio-99, Major Alarm, Link Down >
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
SWLab-100, Minor Alarm, Link Down >
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.
**********************************************************
*
* Welcome to the Proteus AMT Radio
*
* (c) 2002-2006, Microwave Networks, Inc.
*
* Software Version: 1.N (2006-07-30)
*
* Capacity: 16 E1 + 8 E1
*
* Bandwidth: IF board not installed
*
* TX Frequency: 13120.000 MHz
*
* RX Frequency: 0.000 MHz
*
* LAN IP Address: 172.16.99.99 MASK 255.255.0.0
*
* WAN IP Address: 172.111.127.1 MASK 255.255.255.252
*
**********************************************************
The product CD includes software release notes that detail new features
and fixes.
Alarms
--------------------------------------------------
Alarm Menu
1. Current Alarms
2. Latched Alarms
3. Alarm Log
4. Change Log
5. Clear All Latched Alarms
0. Exit
NewRadio-99, Major Alarm, Link Down > 1
Alarms include near- and far-end current and latched alarms, the alarm
and change logs, and a command to clear latched alarms. Menus also
support primary and secondary radios in protected radios.
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 Primary [Normal]
2. Far End Primary [Normal]
3. Near End Secondary (Local) [Major]
4. Far End Secondary [N/A]
0. Exit
NewRadio-99, Major Alarm, Link Down > 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
I2C Failure
ODU Telemetry Alarm
AIS Inserted on Tributaries
Custom BER Level
LIM A Tributary 1 RX LOS
Lim A Tributary 3 RX LOS
Lim A Tributary 6 RX LOS
Lim A Tributary 8 RX LOS
Other Radio Alarm
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.
--------------------------------------------------
Near End Secondary Alarm Log Menu
1. Show Alarm Log
2. Reset Alarm Log
0. Exit
NewRadio-99, Major Alarm, Link Down > 1
2004/02/24 11:29:55, NewRadio-99, (set), ODU Telemetry Alarm, I: 33, O: 0
2004/02/24 11:29:55, NewRadio-99, (set), IF Board PLL Lock, I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), Lim A Tributary 8 RX LOS, I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), Lim A Tributary 6 RX LOS, I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), Lim A Tributary 3 RX LOS, I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), LIM A Tributary 1 RX LOS, I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), AIS Inserted on Tributaries
2004/02/24 11:29:54, NewRadio-99, (set), Custom BER Level, I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), Rx BER > 10^-6, I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), Rx BER > 10^-3, I: 33, O: 0
Press any key to continue (CTRL-C to abort)...
2004/02/24 11:29:54, NewRadio-99, (set), Relay 1 , I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), Hot Standby High Priority Alarm
2004/02/24 11:29:54, NewRadio-99, (set), Modem Receive Fail, I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (clr), Relay 1 , I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (clr), Hot Standby High Priority Alarm
2004/02/24 11:29:54, NewRadio-99, (set), Relay 1 , I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), Hot Standby High Priority Alarm
2004/02/24 11:29:54, NewRadio-99, (set), Major Alarm - Latched, I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), Major Alarm Summary, I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), Modem Rx Frame Loss, I: 33, O: 0
Press any key to continue (CTRL-C to abort)...
2004/02/24 11:29:54, NewRadio-99, (set), Relay 2 , I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), Hot Standby Low Priority Alarm
2004/02/24 11:29:54, NewRadio-99, (set), Secondary Power Supply Failure
2004/02/24 11:29:54, NewRadio-99, (clr), Relay 2 , I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (clr), Hot Standby Low Priority Alarm
2004/02/24 11:29:54, NewRadio-99, (set), Relay 4 , I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), Relay 2 , I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), Hot Standby Low Priority Alarm
2004/02/24 11:29:54, NewRadio-99, (set), Minor Alarm - Latched, I: 33, O: 0
2004/02/24 11:29:54, NewRadio-99, (set), Minor Alarm Summary, I: 33, O: 0
End
--------------------------------------------------
Near End Secondary Change Log Menu
1. Show Change Log
2. Reset Change Log
0. Exit
NewRadio-99, Major Alarm, Link Down > 1
2004/02/24 14:46:47, 29, Admin, 172.16.99.22, Command Processor Command
2004/02/24 14:44:52, 3, Admin, 172.16.99.22, Command Processor Command
2004/02/24 14:44:24, 3, Admin, 172.16.99.22, Command Processor Command
End
Performance
-------------------------------------------------
Performance
1. Near End Primary
2. Far End Primary
3. Near End Secondary (Local)
4. Far End Secondary
5. Reset All Stats
0. Exit
NewRadio-99, Major Alarm, Link Down > 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
NewRadio-99, Major Alarm, Link Down >
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 Primary Performance (Last Second)
Near End Primary
Elapsed Seconds: N/A
Available Seconds: N/A
Errored Seconds: N/A
Severely Errored Seconds: N/A
Bit Error Rate: N/A
(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,
which include Min, Max, and Average RSL.
Near End Secondary Performance (Custom)
Near End Secondary
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. Uploaded files go your TFTP server (not pro-
vided) at the interval that you set, or you can request a manual upload
anytime.
Enter the IP address of the TFTP server in the Utilities menu, Download
selection. The file saves to the directory you configure in your TFTP
server application.
--------------------------------------------------
Near End Secondary Performance History Menu
1. Data Collection Enable [OFF]
2. Data Collection Interval [15 Seconds]
3. Collected Variables [5 selected]
4. Upload Filename [phist.csv]
5. Upload Interval [0 Seconds]
6. Storage Info
7. Show History
8. Request Manual Upload
9. Clear History
0. Exit
NewRadio-99, Major Alarm, Link Down >
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
NewRadio-99, Major Alarm, Link Down >
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 Primary
2. Far End Primary
3. Near End Secondary (Local)
4. Far End Secondary
0. Exit
NewRadio-99, Major Alarm, Link Down > 1
--------------------------------------------------
Near End Primary Tributary Loopback Menu
1. Tributary Local Loopback
2. Tributary Remote Loopback
0. Exit
NewRadio-99, Major Alarm, Link Down >
NE/FE Local
Local Aggregate
Tributary
Loopback
Loopback
IDU
LIM-A ODU
Processing
Multiplex Coding
and and RF
IF
Frame Modem Processing
LIM-B
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 Primary
2. Far End Primary
3. Near End Secondary (Local)
4. Far End Secondary
0. Exit
NewRadio-99, Major Alarm, Link Down > 1
--------------------------------------------------
Near End Primary Tributary BER Test
1. Tributary BER Test Mode
2. Tributary BER Test Results
3. Clear Tributary Results
0. Exit
NewRadio-99, Major Alarm, Link Down > 1
--------------------------------------------------
Near End Primary Tributary BER Test Mode
1. LIM A, Trib 1 [OFF]
2. LIM A, Trib 2 [OFF]
3. LIM A, Trib 3 [OFF]
4. LIM A, Trib 4 [OFF]
5. LIM A, Trib 5 [OFF]
6. LIM A, Trib 6 [OFF]
7. LIM A, Trib 7 [OFF]
8. LIM A, Trib 8 [OFF]
9. LIM A, Trib 9 [OFF]
10. LIM A, Trib 10 [OFF]
11. LIM A, Trib 11 [OFF]
12. LIM A, Trib 12 [OFF]
13. LIM A, Trib 13 [OFF]
14. LIM A, Trib 14 [OFF]
15. LIM A, Trib 15 [OFF]
16. LIM A, Trib 16 [OFF]
17. LIM B, Trib 1 [OFF]
0. Exit
NewRadio-99, Major Alarm, Link Down >
The displays with the BER test results update every five seconds.
--------------------------------------------------
Aggregate BER Test
1. Near End Primary [OFF]
2. Far End Primary [OFF]
3. Near End Secondary (Local) [OFF]
4. Far End Secondary [N/A]
5. Clear All Agg BER Results
0. Exit
NewRadio-99, Major Alarm, Link Down > 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
NewRadio-99, Major Alarm, Link Down > 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 Primary IDU
1. Near End Primary [NewRadio-100]
2. Far End Primary [NewRadio-101]
3. Near End Secondary (Local) [NewRadio-99]
4. Far End Secondary [N/A]
0. Exit
NewRadio-99, Major Alarm, Link Down > 1
--------------------------------------------------
Near End Primary IDU Configuration Menu
1. Radio Name [NewRadio-100]
2. Inventory
3. Admin Password
4. Guest Password
5. Set Clock [2004-3-11,15:40:23]
0. Exit
NewRadio-99, Major Alarm, Link Down >
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 Primary
Image Booted: Secondary
Odu Version:
Odu Serial #: 3
Odu Firmware Version: 53
Motherboard Part Number: 8000567-00
Motherboard Version:
Motherboard Serial #: HI1202020247
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 Primary [13120.000 MHz]
2. Far End Primary [12854.000 MHz]
3. Near End Secondary (Local) [13120.000 MHz]
4. Far End Secondary [N/A]
0. Exit
NewRadio-99, Major Alarm, Link Down > 1
--------------------------------------------------
Near End Primary 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
NewRadio-99, Major Alarm, Link Down >
--------------------------------------------------
Configuration Menu
1. IDU
2. ODU
3. LIMs / Modulation
4. Service Channels
5. Hot Standby
6. IP
7. Reset to factory Settings
0. Exit
NewRadio, Minor Alarm, Link Down > 4
Hot Standby lets you set the radio protection mode.
--------------------------------------------------
Protection Configuration Menu
1. Near End Protection Mode [Non-Protected]
2. Far End Protection Mode [Non-Protected]
3. Online Request [OFF]
4. Near End Status
0. Exit
NewRadio, No Alarms, Link Up >
IP Configuration lets you set the radio IP address, IP mask, and routing.
You can enter static routing information of up to 50 routes or use RIP
(routing information protocol). RIP automates the population of routing
tables on your network.
--------------------------------------------------
IP Configuration Menu
1. LAN Interface [172.16.99.96]
2. WAN Interface [0.0.0.0]
3. Routing Table
0. Exit
, No Alarms, Link Up > 1
--------------------------------------------------
LAN Interface Configuration
1. LAN IP Address [172.16.99.96]
2. LAN IP Mask [255.255.0.0]
3. LAN Routing Config
0. Exit
, No Alarms, Link Up > 1
Please enter new value for LAN Address (in dotted decimal):
--------------------------------------------------
LAN Port Routing Settings
1. Routing Protocol [None]
2. Enable Custom Advertisement [OFF]
3. Custom Advertisement Address [0.0.0.0]
4. Custom Advertisement Mask [0.0.0.0]
0. Exit
, No Alarms, Link Up > 1
Enter new value for LAN Routing Protocol:
1. Disabled
2. RIP
Select:
The Service Channel Menu lets administrators set the auxiliary channel
data rate and the orderwire mode and station code.
--------------------------------------------------
Service Channels
1. Near End (Local) [9600/19200/VOICE-123]
2. Far End [9600/19200/VOICE-000]
0. Exit
SWLab-100, No Alarms, Link Up > 1
--------------------------------------------------
Near End Service Channel Menu
1. Auxiliary Channel 1
2. Auxiliary Channel 2
3. Orderwire Channel
0. Exit
SWLab-100, No Alarms, Link Up > 1
--------------------------------------------------
Near End Port 1 Auxiliary Channel 1
1. Baud Rate [9600]
2. Parity [ODD]
3. Polarity [INVERT BOTH]
4. Stop Bits [2]
0. Exit
NewRadio, No Alarms, Link Up > 1
Enter new value for Aux Chnl Rate (9600 or 19200):
--------------------------------------------------
Near End Orderwire Menu
1. Orderwire Mode [VOICE]
2. Orderwire Station Code [123]
0. Exit
NewRadio,, No Alarms, Link Up >
The orderwire voice mode is for EOW with optional DTMF handset. In
data mode, the orderwire converts data at OW1 to an 'over-the-link'
64-kbps clear channel. OW2 and the handset interface become inactive
in data mode.
Utility
1 Firmware files include '.hex' files for application images, and '.mni' for IDU and
LIM programable logic.
Get a trial version of an IDU and LIM 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
--------------------------------------------------
Download Menu
1. Begin Download
2. Flash Destination [Bootloader Code]
3. Source Port [Ethernet]
4. TFTP File Name [plusdemo.hex]
5. TFTP Server Address [172.16.206.91]
0. Exit
NewRadio, Minor Alarm, Link Up > 0
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
NewRadio, 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
NewRadio, 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 radios allows IP access 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 simply the 10/100BaseT Ethernet
interface accessed at the RJ-45 connector on the radio front panel. It is
called LAN because it immediately communicates with any Ethernet de-
vice on the same subnet, 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 4 decimal numbers ranging from 0 to 255. In a subnet
mask, the first, or most significant, bit of the mask must be set to binary 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. LIMs / Modulation
4. Service Channels
5. Hot Standby
6. IP
7. Alarms
8. Reset to factory Settings
0. Exit
NewRadio-99, Major Alarm, Link Down > 6
--------------------------------------------------
IP
1. Near End Primary [172.16.200.100]
2. Far End Primary [172.16.200.101]
3. Near End Secondary (Local) [172.16.99.99]
4. Far End Secondary [N/A]
0. Exit
NewRadio-99, Major Alarm, Link Down > 1
--------------------------------------------------
Near End Primary IP Configuration Menu
1. LAN Interface [172.16.200.100]
2. WAN Interface [172.111.1.1]
3. PPP Interface [172.9.111.121]
0. Exit
NewRadio-99, Major Alarm, Link Down > 2
--------------------------------------------------
Near End Primary WAN Interface Configuration
1. WAN IP Address [172.111.1.1]
2. WAN IP Mask [255.255.255.252]
3. WAN Routing Config [None]
0. Exit
NewRadio-99, Major Alarm, Link Down >
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 radio.
IP Configuration Menu
1. LAN Interface [172.16.20.201]
2. WAN Interface [172.40.200.201]
3. PPP Interface [172.25.200.225]
4. Routing Table
0. Exit
TopRadio, No Alarms, Link Up >
ID Destination Mask Next Hop Type Int
1 0.0.0.0 0.0.0.0 172.16.40.1 IND 2
2 127.0.0.0 255.0.0.0 127.0.0.1 DIR 1
3 172.16.0.0 255.255.0.0 172.16.99.100 DIR 2
4 172.16.200.100 255.255.255.255 127.0.0.1 IND 1
5 172.17.1.0 255.255.255.252 172.17.1.1 DIR 3
6 172.17.1.1 255.255.255.255 127.0.0.1 IND 1
7 172.18.0.0 255.255.0.0 172.17.1.2 IND 3
--------------------------------------------------
Route Table
1. Add Route
2. Delete Route
3. Change Default Route [172.16.40.1]
0. Exit
TopRadio, No Alarms, Link Up >
The table is broken into six columns: ID, Destination, Mask, Next Hop,
Type, and Interface. The ID identifies a route, making 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 example, 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 ad-
dress 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 forward it on to the de-
vice 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 destina-
tion (DIR) or to another router (IND). The interface field tells us which
interface the radio will route the packet on. INT1 is the loopback inter-
face, INT2 is the LAN interface, and INT3 is the WAN interface. ID7 is
routing packets across the WAN interface.
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 enter into a routing table. Static routes
PCs to monitor radios stay in the routing table across power-ups until the you delete them. The
on a different subnet. exception is when an interface goes down and all the routes to that inter-
See the following page. face temporarily become inactive. This can occur when the WAN inter-
face fails down as a result of microwave link or radio failure. When the
interface 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 or MNI Protection rout-
ing (page D-6 and page D-10), 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.
Advantages of RIP
RIP helps install network communications much faster on large networks
because you don't have to setup static routing tables in any of the radios.
As new radios are added you do not have to re-visit all the other radios in
the network to update their routing tables.
When you have a protected network with multiple paths, RIP will find
the shortest path in terms of routing hops. If that path breaks for any rea-
son, RIP will find an alternate path and resume communications.
NOTE: When you install routers with protected radios you cannot use
MNI Protection Routing you must use RIP.
Disadvantages of RIP
Network Size: The RIP standard is limited to 15 routing hops in a single
line. Since each radio performs routing, there are two routing hops for
each non-protected radio link. So a network that contains more than
seven microwave links in a single line will not be able to establish com-
munications across the network using RIP alone.
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.
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.
Ethernet connection
microwave link
LAN 172.16.5.2 172.16.13.1 LAN
WAN 172.16.6.1 172.16.12.2 WAN
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.
microwave link
Ethernet connection
RADIO CONFIGURATION:
Enter the radio IP address and its twin (primary and secondary) for each hot-standy radio.
Set the routing protocol to RIP. Enable CUSTOM ADVERTISEMENT on the first radio of each subnet in your larger
network to bypass the 15-radio limitation of RIP.
Monitor a radio hop by connecting a PC running EM, CTI, or Telnet to an IP address of one of the radios on the same
subnet as the PC, or add a static route on the PC to the subnet and then connect to the radio IP using EM, CTI, or
Telnet. To set a static route use the ROUTE command (see Windows™ Help for command usage).
With MNI protection routing active the radio requires twin IP addresses.
The twin is the LAN address of the radio on the other side of the Redun-
dancy Switch Unit (RSU). In the example, for TopRadioPri the twin ad-
dress is 172.16.200.101, for TopRadioSec the twin address is
172.16.200.100, for BotRadioPri the twin address is 172.18.200.102, and
for BotRadioSec the twin address is 172.18.200.101.
The default Protection Also required for MNI protection routing to work is a port number. The
Routing Port number default value of 3764 is the port that MNI registered with the Internet
is always 3764. Assigned Numbers Authority (IANA) for MNI protection routing. There
should be no conflicts with other devices when using this port, but if
there are, radio management software provides an option to change the
port value.
MNI protection routing uses information known about the radio protec-
tion scheme with messages passed between twins to set up routing tables
properly on all four radios.
When the system is powered, assuming there are no failures, both pri-
mary radios and both secondary radios will be on-line. TopRadioPri will
automatically have routes to networks it is directly connected to
172.16.0.0/16 and 172.17.1.0/29. Additionally, TopRadioPri will learn
the route to 172.18.0.0/16 via 172.17.1.2. TopRadioSec, however, will
only have the automatic route to 172.16.0.0/16 because its WAN port
will not be active. It will learn the route to 172.17.1.0/29 and
172.18.0.0/16 from TopRadioPri at 172.16.200.100. The same happens
with BotRadioPri and BotRadioSec on the other side of the link. So, you
can access any of the other three radios via IP data.
If we assume that a switch occurs where TopRadioPri goes off-line and
TopRadioSec comes on-line, then the routing tables change. TopRadi-
oSec will delete its routes via TopRadioPri, and add the automatic route
to 172.17.1.0/29, since its WAN interface is now active. Additionally, it
will learn the route to 172.18.0.0/16 via 172.17.1.2. It will then advertise
this information to TopRadioPri, which will add routes to 172.17.1.0/29
and 172.18.0.0/16 via TopRadioSec. When this happens, BotRadioPri
also has to change its route to 172.16.0.0/16 from 172.17.1.1 (TopRadio-
Pri's now-inactive WAN port) to 172.17.1.3 (BotRadioPri's now-active
WAN port). Once all this occurs, any radio in the system may communi-
cate with any three radios in the system again. This typically takes less
than 5 seconds to occur.
NOTE: When you install routers with protected radios you cannot use MNI
Protection Routing you must use RIP.
If you have a loop of protected radios, MNI protection routing will not
re-direct packet direction if a link totally fails on both the primary and
secondary sides.
NOTE: Reboot each IDU after changing routing protocol. Ensure the port
number is 3764 after reboot, if not, set the port number and reboot
again.
NOTE These steps assume you have not setup radio IP addresses in
hot-standby configuration. If you have, skip to steps that set routing
protocol and port number (d and h).
1. First, log into the CTI menu of the near-end primary radio
(TopRadioPri) to configure the radio IP.
Selection numbers are a. From the main menu select 4, 6, 1, 1 to navigate to the NE primary
provided here as short LAN IP address entry
notation. Press Enter b. Enter the LAN IP address (e.g. 172.16.200.100)
after each selection. c. Select 2 and enter the LAN IP mask (e.g. 255.255.0.0)
d. Select 3, 1, 3 to enable MNI protection routing on port 3764
e. Select 0, 0, 2, 1 to navigate to the WAN IP address entry
f. Enter the WAN IP address (e.g. 172.17.1.1)
g. Select 2 and enter the WAN IP mask (e.g. 255.255.255.248)
h. Select 3, 1, 3 to enable MNI Protection Routing
i. Select 0, 0, 0, 0, 0 to navigate to the main menu
j. Select 5, 5 to reboot to the primary image location.
k. Ensure all parameters are correct.
Reboot each IDU after changing the routing protocol. Ensure that the
port number is 3764 after reboot, if not, manually set it and reboot
again.
2. Next, configure IP on the near-end secondary radio (TopRadioSec)
a. Select 4, 6, 3, 1 to navigate to the NE secondary LAN IP address
entry
b. Enter the LAN IP address (e.g 172.16.200.101)
c. Select 2 and enter the LAN IP mask (e.g 255.255.0.0)
d. Select 3, 1, 3 to enable MNI protection routing on port 3764
e. Select 0, 0, 2, 1 to navigate to the NE secondary WAN IP address
entry
f. Enter the WAN IP address (e.g. 172.17.1.3)
g. Select 2 and enter the WAN IP mask (e.g. 255.255.255.248)
h. Select 3, 1, 3 to enable MNI protection routing
i. Select 0, 0, 0, 0, 0 to navigate to the main menu
j. Select 5, 5 to reboot to the primary image location.
k. Ensure all parameters are correct.
Reboot each IDU after changing the routing protocol. Ensure that the
port number is 3764 after reboot, if not, manually set it and reboot
again.
3. Now, log into the far-end primary radio (BotRadioPri in this example).
a. Select 4, 6, 2, 1 to navigate to the FE primary LAN IP address entry
b. Enter the LAN IP address (e.g 172.18.200.101)
c. Select 2 and enter the LAN IP mask (e.g 255.255.0.0)
d. Select 3, 1, 3 to enable MNI protection routing on port 3764
e. Select 0, 0, 2, 1 to navigate to the FE primary WAN IP address entry
NE - A (primary) FE - A (primary)
LAN 172.16.200.100 LAN 172.18.200.101
MASK 255.255.0.0 MASK 255.255.0.0
MNI Protection/Port 3764 MNI Protection/Port 3764
WAN 172.17.1.1 WAN 172.17.1.2
MASK 255.255.255.248 MASK 255.255.255.248
Computer IP 172.16.x.x
Route:
172.17.0.0, NE - B (secondary) FE - B (secondary)
255.255.255.248, LAN 172.16.200.101 LAN 172.18.200.102
172.16.200.100 MASK 255.255.0.0 MASK 255.255.0.0
MNI Protection/Port 3764 MNI Protection/Port 3764
WAN 172.17.1.3 WAN 172.17.1.4
MASK 255.255.255.248 MASK 255.255.255.248
5. All four radios now know how to route protection switching. The
computer connected to the radio interface must also know how to route
on radio network to see all four radios, no matter which IDU is online.
In the example, the computer should have an IP address of 172.16.X.X,
where X can be any value except 0 or 255.
a. Confirm this with ROUTE PRINT at the command prompt. If the route
is not there, configure the routing table on your computer using
ROUTE. The command usage is ROUTE [-p] [command]
[destination] [MASK netmask] [gateway]
b. Open a DOS window (command prompt)
c. At the command prompt type: route add –p [destination]
(172.17.0.0) mask [netmask] (255.255.255.248)
[gateway] (172.16.200.100) and press Enter
d. Then type: route add –p [destination] (172.18.0.0)
mask [netmask] (255.255.0.0) [gateway]
(172.16.200.100) and press Enter
The –P switch is used with the ADD command to make the route
persistent across power cycles and reboots. If you followed these
steps, the computer should see all four radios, no matter which IDU
is online.
Configuring Protection Routing Using EM
Set IP addresses and masks to the values previously described using the
Configuration/IP Addresses selection of EM. You can configuration all
sites using the two setup displays. Reboot the IDU when complete.
Introduction
Virtual LAN, VLAN, is a network of computers that behaves as if con-
nected to the same wire even though physically located on different seg-
ments of a LAN. VLANs are configured through software rather than
physical cable and hardware, which makes them extremely flexible, and
organizations can segregate network communication with less concern
about physical location. Along with mobility, VLAN provides traffic
management capabilities such as traffic class prioritization and limiting
data rates.
You set VLAN membership with software on the device. LAN manage-
ment on the Proteus AMT radio works in two modes: a port-based ap-
proach, and a frame-tagging approach. Segment LIM ports to a specific
VLAN, or filter MAC-layer frames using VLAN identity tags in the
packet frames.
VLAN Features
VLAN implementation on Proteus AMT radios feature:
Each LAN is physically cabled into a specific port on the VLAN switch.
A network manager can use EM or the CTI application to set member-
ship mode. To use EM to configure port-based membership see ”Setting
Up the Port-Based VLAN Configuration with EM” on page E-8.
There are four traffic classes: 0, 1, 2, and 3. Traffic class 3 has the high-
est priority, while 0 has lowest priority.
You can enable traffic classes with VLANs disabled. Parameters relating
to traffic class – order, weighting, mapping, and rate limiting – will not
work with traffic class disabled. Table E-A details the VLAN configu-
ration settings for the 100Base-T LIM.
VLAN Enable Switch LIM from a standard learning bridge to a 802.1Q VLAN. The VLAN membership and packet for-
warding rules get set from VLAN configuration table and port defaults.
Ignore When set to IGNORE the LIM port ignores any VLAN ID (VID) tag on incoming Ethernet frames, and adds
Incoming Tags a tag based on the ingress port number. The LIM preserves the incoming tag across the link.
Use to switch from a tag-based (USE TAGS) to port-based VLAN.
Traffic Class Sets the device to recognize different traffic classes. Required for rate limiting or for prioritizing packets
Enable based on ingress port, 802.1p priorities, or differentiated service (DiffServ) values.
Traffic Class Determines how packets separate into traffic class. Use the priority field of the
Order VLAN tag, the DiffServ information in the IP header, or the default traffic class of
the port, or combine the three. For example, look at VLAN tag first, then, if there is
no VLAN tag, the IP header, and then, without DiffServ information in the IP header,
use the default traffic class.
Traffic Class Sets how the 100BaseT LIM queues packets for transmission. If UNWEIGHTED, high traffic-class packets
Weighted transmit before low traffic-class packets. If WEIGHTED, packets transmit with 8-4-2-1 weighting. Use
weighting to ensure low traffic-class streams do not completely shut down during extreme activity.
Traffic Class These parameter selections let you define how IP differentiated services (DiffServ), called Type of Ser-
Mapping vice (TOS), or 802.1p priorities are mapped into traffic classes.
Type of Service Differentiated services is a method that providers may use to guarantee a particular level of QoS (qual-
(DiffServ) ity of service) to their subscribers. The selection maps the six-bit differentiated service fields defined in
IETF RFC 2474 to the four traffic classes allowed by the 100BaseT LIM.
The DiffServ field is found in the second octet of an IP header, where the six most significant bits define
the differentiated services. The two least significant bits are now unused and are assumed to be zero.
The value that goes into the map is the value of the entire octet, meaning that any value entered must
be evenly divisible by four. Each of the four traffic classes has a maximum DiffServ value that defines
a “watermark” point between traffic classes. Below is a For example, take the following configuration:
Important: the maximum value for traffic class 3 must be greater than the maximum value for traffic
class 2, which much be greater than the maximum value for traffic class 1, etc. Therefore, first set the
value for traffic class 3, followed by traffic class 2, then 1, and finally traffic class 0.
VLAN Priority VLAN priorities are set by the priority bits defined in IEEE 802.1p (now in IEEE 802.1D). The standard
defines three priority bits; making eight levels of priority (0 to 7– 7 being highest).
Priorities determine the order in which traffic,
for each of the four traffic classes (0 to 3), gets
transmitted. The priority may or may not be
rate-limited, depending upon how it has been
configured
Unlike DiffServ mapping, you can assign the
traffic classes in any order.
Link Loss Sets how the device behaves if the microwave link drops-off.
Forwarding
NONE all ports stay enabled
ALL all ports disabled
LINK PORT ONLY the port transmitting packets (invisible to the user) disables. Use when the radio is
used to connect networks locally, but you don’t want the buffers in the device to fill
up with data destined for the (dead) microwave link.
Figure E-2 shows how packets are forwarded when using port-based
VLAN. Although the radio link operates as a single connection,
port-based VLAN operates like the four ports on each radio are individ-
ual links.
Table E-B, starting on the next page, details the port-based VLAN con-
figuration settings.
Default VLAN ID Works with VLAN enabled. Use this parameter to assign a VLAN ID to any untagged packet entering
this port. This will also be the VLAN ID assigned with IGNORE INCOMING TAGS enabled.
Ingress Filtering Works with VLAN enabled. With ingress filtering OFF, the port allows any packet to enter, and then
routes the packets based on VLAN ID and the VLAN tables. Packets which are members of VLANs
not listed in the VLAN table, are dropped.
With ingress filtering ON the port only accepts packets with VLAN IDs in which the port is a member.
Setting IGNORE INCOMING TAGS overrides this option.
Line Type In auto-negotiate the port adjusts data rate and duplex type. Available modes: 10BaseT Half Duplex,
100 BaseT Half Duplex, and 100 BaseT Full Duplex.
Default Traffic The traffic class assigned to all ingress packets on the port, unless the packet has VLAN priority tag
Class or IP DiffServ information and those features are enabled (see traffic class order and mapping).
Ingress Rate Works with traffic class enabled. Set the ingress rate limit of each of the four traffic classes.
Traffic class 0 packets can be set to be limited to from 128 Kbps to 8 Mbps. All other traffic classes
can be set either equal to, or twice, the rate of the next lower traffic class, for a maximum rate limit of
64 Mbps for traffic class 3 packets.
Also, all the rate limits may be set to UNLIMITED.
2. Set all frames to UNTAGGED so that packets leaving one radio are the
same as packets that enter the opposite side of the link.
3. Set the default VLAN IDs for each port. In this example, the default
VLAN ID for port 1 should be 1. This means that any packet that
comes in Port 1 is assigned to VLAN 1, which has Port 1 as the only
member in the group. So, the packet cannot be sent to any of the
other ports. Similarly, the default VLAN ID for Port 2 is 2, and so
on.
This means that if the device receives packets that have VLAN tags
on them, these tags are ignored and port-based VLAN takes
precedence.
When the packet leaves from the radio link, the original VLAN tag
remains for use on the network.
An untagged frame comes in port 2. The port adds a VLAN tag with
VLAN ID 2. The tagged frame goes across the microwave link. If the
LIM on the far end has the same settings, the tagged packet enter the
LIM from the radio side, and goes to port 2 (the only member port of
VLAN-Id 2). The port removed the VLAN ID tag, and the packet trans-
mits to the network.
NOTE: Since ports add VLAN ID tags to data transmitted over the link,
extra overhead is used, and the device does not operate at 100%
throughput.
Figure E-3. Element Manager VLAN Port Configuration Screens - Rate Limiting Example
When ports try to output more packets than the rate limiting set up, the
excess packets get dropped. Flow control is not used in this case, so that
the rejection of low-priority packets do not affect the acceptance of
high-priority packets.
If the port inputs exceed the overall bandwidth of the radio, then the de-
fault traffic class and traffic class weighting for the port decide which
packets get dropped.
For example, with 16 Mbps of data on each of ports 2, 3, and 4 (the max-
imum rate limiting allows), and 70 Mbps of data on port 1, then the total
data rate attempted to be sent through the switch is 118 Mbps. If the ra-
dio throughput is 100 Mbps, then 18 Mbps of data is dropped.
Note: In the example above, data will not flow through port 4 at all.
If you set traffic class weighting in the example above to WEIGHTED, the
device will then send eight packets of the highest traffic class, four pack-
ets of the next highest traffic class, two packets from the next highest
traffic class, and one packet from the lowest traffic class.
In the example above, most of the data still drops from port 4, but it
would have some of its pass through the radio link.
Traffic Class Enable Lets the device recognize different traffic classes. Re-
quired for rate limiting or for prioritizing packets by type
of service.
Traffic Class Order Organizes packets into traffic classes. Each port has
four classes. Selections for priority field of the VLAN tag,
the type of service information in the IP header, or the
default port priority. Or, selection for a combination of
the three. For example, first look at the VLAN tag, then
if no VLAN tag–the IP header, and then if no traffic class
information in the IP header–use default priority.
Traffic Class Weighted Sets the device egress policy. If OFF, high priority pack-
ets always egress before low priority packets. If ON, the
packets egress with 8-4-2-1 weighting.
Link Loss Forwarding Sets device behavior if the microwave link fails. If set to
NONE, all ports on the device remain enabled at all
times. If set ALL, all ports disable on a failed link. If set
LINK PORT ONLY, the port that sends packets across the
link (indistinct) turns off on a link failure. Useful when the
radio connects networks locally, but you don't want de-
vice buffers to fill with data destined for the failed link.
802.1Q VLANs Must be ON to enable VLAN capability.
Ignore incoming tags This tells the device to ignore any incoming tags, and
add its own tag based upon the ingress port. The incom-
ing tag will be preserved across the link.
Default Traffic Class The traffic class you assign to all ingress packets on the
port, unless the packet has VLAN priority tag or IP DiffServ
information and you enabled those features (Traffic Class
menu, page E-18).
Default VLAN Id VID assigned to any untagged packet entering this port. Al-
so, the VID assigned if ignore incoming tags is ON.
Ingress Filtering If ON, the port rejects packets that do not have a VID of the
VLAN group in which the port is a member.
Line Type If AUTO-NEG, the port auto-negotiates the data rate and du-
plex type. Also has selections for 10BaseT Half Duplex,
100BaseT Half Duplex, and 100BaseT Full Duplex.
Rate Limiting Select the ingress rate limit for each of the four priority
classes. Priority 0 packets can be limited from 128 KBPS to
8 MBPs. All other priorities can be either equal to or twice
the rate of the next lower priority for a maximum rate limit
of 64 Mbps for Priority-3 packets. All rate limits can also be
set to UNLIMITED.
have VLAN tags on them, these tags are ignored and port-based
settings take precedence.
When the packet leaves the radio link to a network device, the
original VLAN tag remains for use on that network.
The following screen shows the VLAN configuration table and configu-
ration selections. When adding an entry, CTI asks for a VLAN ID and
name, and then asks if each of ports 1 to 4 should be a member port and
untagged port. Once you answer the set up prompts, CTI adds the VLAN
entry.
ID VID Name Egress Untagged
65 1 1 1
66 2 2 2
67 3 3 3
68 4 4 4
----------------------------------------
Near End Secondary LIM B VLAN Table
1. Add Vlan Entry
2. Delete Vlan Entry
0. Exit
NewRadio, No Alarms, Link Up >1
The following is the 802.1P traffic class menu. This menu lets you map
the priority field of the VLAN tag (a value from 0 to 7) to a priority traf-
fic class within the device (a value from 0 to 3).
Near End Secondary LIM B Traffic Class Menu
1. Priority 0 TC [0]
2. Priority 1 TC [1]
3. Priority 2 TC [2]
4. Priority 3 TC [3]
5. Priority 4 TC [3]
6. Priority 5 TC [3]
7. Priority 6 TC [3]
8. Priority 7 TC [3]
0. Exit
NewRadio, No Alarms, Link Up >1
This selection lets you map the type of service field in IP headers. It uses
bits 7:2 of the field, so all values input into this table must be a multiple
of 4 and no greater than 252. Each entry represents the maximum service
value for mapping into one of the four priority traffic classes on the de-
vice.
In the example above, IP data with a TOS field of 20 or below goes to
traffic class 0, with a TOS field between 24 and 124 to traffic class 1,
with a TOS field between 128 and 200 to traffic class 2, and IP traffic
with a TOS field between 204 and 252 goes to traffic class 3.
Overview
The Federal Communication Commission (FCC) establishes and en-
forces frequency coordination in the United States to ensure that the fre-
quency spectrum you want to use will not interfere with existing, or pro-
posed, microwave paths and stations. FCC rules, Part 101, contains
procedures for the filing radio station licenses in the fixed microwave
services.
The Proteus AMT radio is very flexible, and you can configure an in-
stalled radio remotely with the associated radio management software.
This flexibility also lets you potentially set a radio mode that exceeds
your licensed emission.
Once you license your radio it must remain in the mode indicated by
your license. This is most notable for 100BaseT configurations, which
have high throughput and high gain modes. High throughput mode uses
32QAM modulation, therefore the frequency coordination uses the lower
power output associated with 32QAM. High gain mode increases trans-
mitter output power, but violates the license of a high throughput radio.
Table F-A and Table F-B provide the configuration information needed
for FCC license applications.
Table F-B Frequency Licensing Data; All Data Rates & LIM Profile
BW (MHz) MOD Data Rate LIM A LIM B Aggregate Rate (bps) Emission Designator
3.5 4-QAM 2E1 2XE1 5292000 3M50D7W
3.5 4-QAM 2XE1 5292000 3M50D7W
3.5 8-PSK 4E1 4XE1 10600000 3M50D7W
3.5 16-QAM 2XE1 2XDS1 8740000 3M50D7W
3.5 4-QAM 100BT 100BT 5832000 3M50D7W
3.5 8-PSK 100BT 8712000 3M50D7W
3.5 8-PSK 100BT 100BT 8712000 3M50D7W
3.5 4-QAM 100BT 100BT 5832000 3M50D7W
3.5 8-PSK 2E1+100BT 2XE1 100BT 8712000 3M50D7W
3.5 4-QAM 2XE1 100BT 5832000 3M50D7W
5 4-QAM 4DS1 4XDS1 7968000 5M00D7W
5 16-QAM 8DS1 8XDS1 15936000 5M00D7W
5 16-QAM 2DS1+100BT 2XDS1 100BT 16512000 5M00D7W
5 16-QAM 100BT 100BT 16416000 5M00D7W
5 16-QAM 100BT 100BT 16416000 5M00D7W
5 16-QAM 4DS1+100BT 4XDS1 100BT 16512000 5M00D7W
5 16-QAM 8DS1+100BT 8XDS1 100BT 16512000 5M00D7W
5 4-QAM 100BT 100BT 8208000 5M00D7W
5 4-QAM 100BT 100BT 8208000 5M00D7W
5 4-QAM 2XDS1 100BT 8208000 5M00D7W
5 8-PSK 4DS1+100BT 4XDS1 100BT 12336000 5M00D7W
7 4-QAM 4E1 4XE1 11148000 7M00D7W
7 4-QAM 2XE1 2XDS1 11666000 7M00D7W
7 8-PSK 4XE1 4XDS1 17499000 7M00D7W
7 4-QAM 4XE1 11148000 7M00D7W
7 16-QAM 4XE1 4XE1 22296000 7M00D7W
7 16-QAM 8E1 8XE1 22296000 7M00D7W
7 16-QAM 8XE1 22296000 7M00D7W
7 32-QAM 12E1 8XE1 4XE1 29080000 7M00D7W
7 32-QAM 4XE1 8XE1 27900000 7M00D7W
7 32-QAM 12XE1 27900000 7M00D7W
7 4-QAM 100BT 100BT 11664000 7M00D7W
7 16-QAM 100BT 23256000 7M00D7W
7 16-QAM 100BT 100BT 23256000 7M00D7W
7 4-QAM 100BT 100BT 11664000 7M00D7W
7 32-QAM 2E1+100BT 2xE1 100BT 29160000 7M00D7W
7 4-QAM 2XE1 100BT 11664000 7M00D7W
7 32-QAM 4E1+100BT 4xE1 100BT 29160000 7M00D7W
7 4-QAM 4XE1 100BT 11664000 7M00D7W
7 16-QAM 8E1+100BT 8XE1 100BT 23328000 7M00D7W
7 32-QAM 8XE1 100BT 29160000 7M00D7W
7 32-QAM 12E1+100BT 12XE1 100BT 29160000 7M00D7W
10 4-QAM 8DS1 8XDS1 16608000 10M0D7W
10 8-PSK 12DS1 12XDS1 24912000 10M0D7W
10 8-PSK 8XDS1 4XDS1 24912000 10M0D7W
10 16-QAM 16DS1 16XDS1 33216000 10M0D7W
10 16-QAM 8XDS1 8XDS1 33216000 10M0D7W
10 32-QAM 24DS1 16XDS1 8XDS1 41616000 10M0D7W
10 32-QAM 100BT 100BT 41600000 10M0D7W
Table F-B Frequency Licensing Data; All Data Rates & LIM Profile (continued)
BW (MHz) MOD Data Rate LIM A LIM B Aggregate Rate (bps) Emission Designator
10 32-QAM 100BT 100BT 41600000 10M0D7W
10 32-QAM 2DS1+100BT 2XDS1 100BT 41600000 10M0D7W
10 32-QAM 4DS1+100BT 4XDS1 100BT 41600000 10M0D7W
10 32-QAM 8DS1+100BT 8XDS1 100BT 41600000 10M0D7W
10 32-QAM 12DS1+100BT 12XDS1 100BT 41600000 10M0D7W
10 32-QAM 16DS1+100BT 16XDS1 100BT 41600000 10M0D7W
10 4-QAM 100BT 16608000 10M0D7W
10 4-QAM 100BT 100BT 100BT 16608000 10M0D7W
10 4-QAM 2DS1+100BT 2XDS1 100BT 16608000 10M0D7W
10 4-QAM 4DS1+100BT 4XDS1 100BT 16608000 10M0D7W
10 4-QAM 8DS1+100BT 8XDS1 100BT 16608000 10M0D7W
10 8-PSK 12DS1+100BT 12XDS1 100BT 24720000 10M0D7W
10 16-QAM 16DS1+100BT 16XDS1 100BT 33280000 10M0D7W
14 4-QAM E1/DS1 4XE1 4XDS1 23282000 13M7D7W
14 8-PSK 8XE1 8XDS1 34923000 13M7D7W
14 4-QAM 8E1 4XE1 4XE1 22620000 13M7D7W
14 4-QAM 8XE1 22620000 13M7D7W
14 4-QAM 8XE1 22620000 13M7D7W
14 16-QAM 16E1 8XE1 8XE1 45488000 13M7D7W
14 16-QAM 16XE1 45488000 13M7D7W
14 16-QAM 16XE1 45488000 13M7D7W
14 16-QAM 20E1 4XE1 16XE1 45552000 13M7D7W
14 16-QAM 16XE1 4XE1 45552000 13M7D7W
14 32-QAM 24E1 8XE1 16XE1 56880000 13M7D7W
14 32-QAM 16XE1 8XE1 56880000 13M7D7W
14 32-QAM E3+4E1 4XE1 E3 56820000 13M7D7W
14 32-QAM E3 4XE1 56820000 13M7D7W
14 32-QAM E3+8E1 8XE1 E3 56920000 13M7D7W
14 32-QAM E3 8XE1 56920000 13M7D7W
14 4-QAM 100BT 100BT 23292000 13M7D7W
14 4-QAM 100BT 100BT 23292000 13M7D7W
14 32-QAM 100BT 58100000 13M7D7W
14 32-QAM 100BT 100BT 58100000 13M7D7W
14 4-QAM 2E1+100BT 2XE1 100BT 23292000 13M7D7W
14 32-QAM 2XE1 100BT 58100000 13M7D7W
14 4-QAM 4E1+100BT 4XE1 100BT 23292000 13M7D7W
14 32-QAM 4XE1 100BT 58100000 13M7D7W
14 4-QAM 8E1+100BT 8XE1 100BT 23292000 13M7D7W
14 32-QAM 8XE1 100BT 57620000 13M7D7W
14 8-PSK 12E1+100BT 12XE1 100BT 34923000 13M7D7W
14 32-QAM 12XE1 100BT 58100000 13M7D7W
14 16-QAM 16E1+100BT 16XE1 100BT 46488000 13M7D7W
14 32-QAM 16XE1 100BT 58100000 13M7D7W
14 32-QAM 2XE1 DS3 58330000 13M7D7W
20 4-QAM 16DS1 8XDS1 8XDS1 33216000 20M0D7W
20 4-QAM 16XDS1 33216000 20M0D7W
20 8-PSK 24DS1 16XDS1 8XDS1 49680000 20M0D7W
20 8-PSK 28DS1 16XDS1 12XDS1 49856001 20M0D7W
20 16-QAM 32DS1 16XDS1 16XDS1 66432000 20M0D7W
20 8-PSK DS3 DS3 49872000 20M0D7W
Table F-B Frequency Licensing Data; All Data Rates & LIM Profile (continued)
BW (MHz) MOD Data Rate LIM A LIM B Aggregate Rate (bps) Emission Designator
20 16-QAM DS3+2DS1 2XDS1 DS3 66112000 20M0D7W
20 16-QAM DS3+4DS1 4XDS1 DS3 66464000 20M0D7W
20 16-QAM DS3+8DS1 8XDS1 DS3 66384000 20M0D7W
20 32-QAM DS3+12DS1 12XDS1 DS3 82800000 20M0D7W
20 32-QAM DS3+16DS1 16XDS1 DS3 83280000 20M0D7W
20 32-QAM 100BT 100BT 83200000 20M0D7W
20 32-QAM 100BT 100BT 83200000 20M0D7W
20 32-QAM 2DS1+100BT 2XDS1 100BT 83200000 20M0D7W
20 32-QAM 4DS1+100BT 4XDS1 100BT 83200000 20M0D7W
20 32-QAM 8DS1+100BT 8XDS1 100BT 83200000 20M0D7W
20 32-QAM 12DS1+100BT 12XDS1 100BT 83200000 20M0D7W
20 32-QAM 16DS1+100BT 16XDS1 100BT 83200000 20M0D7W
20 32-QAM DS3 100BT 83200000 20M0D7W
20 4-QAM 100BT 100BT 33216000 20M0D7W
20 4-QAM 100BT 100BT 33216000 20M0D7W
20 4-QAM 2DS1+100BT 2XDS1 100BT 33216000 20M0D7W
20 4-QAM 4DS1+100BT 4XDS1 100BT 33216000 20M0D7W
20 4-QAM 8DS1+100BT 8XDS1 100BT 33216000 20M0D7W
20 4-QAM 12DS1+100BT 12XDS1 100BT 33216000 20M0D7W
20 4-QAM 16DS1+100BT 16XDS1 100BT 33216000 20M0D7W
20 16-QAM DS3 100BT 66560000 20M0D7W
25 4-QAM 24DS1 16XDS1 8XDS1 41546000 25M0D7W
25 8-PSK 28DS1 16XDS1 12XDS1 61590000 25M0D7W
25 8-PSK 32DS1 16XDS1 16XDS1 61974000 25M0D7W
25 8-PSK DS3 DS3 61590000 25M0D7W
25 8-PSK DS3+2DS1 2XDS1 DS3 62358000 25M0D7W
25 8-PSK DS3+4DS1 4XDS1 DS3 61350000 25M0D7W
25 8-PSK DS3+8DS1 8XDS1 DS3 62358000 25M0D7W
25 16-QAM DS3+12DS1 12XDS1 DS3 82760000 25M0D7W
25 16-QAM DS3+16DS1 16XDS1 DS3 83144000 25M0D7W
25 32-QAM 2xDS3 DS3 DS3 103860000 25M0D7W
25 32-QAM 100BT 100BT 104080000 25M0D7W
25 32-QAM 100BT 100BT 104080000 25M0D7W
25 32-QAM 2DS1+100BT 2XDS1 100BT 104080000 25M0D7W
25 32-QAM 4DS1+100BT 4XDS1 100BT 104080000 25M0D7W
25 32-QAM 8DS1+100BT 8XDS1 100BT 104080000 25M0D7W
25 32-QAM 12DS1+100BT 12XDS1 100BT 104080000 25M0D7W
25 32-QAM 16DS1+100BT 16XDS1 100BT 104080000 25M0D7W
25 32-QAM DS3+100BT DS3 100BT 104080000 25M0D7W
25 4-QAM 100BT 100BT 41636000 25M0D7W
25 4-QAM 100BT 100BT 41636000 25M0D7W
25 4-QAM 2DS1+100BT 2XDS1 100BT 41636000 25M0D7W
25 4-QAM 4DS1+100BT 4XDS1 100BT 41636000 25M0D7W
25 4-QAM 8DS1+100BT 8XDS1 100BT 41636000 25M0D7W
25 4-QAM 12DS1+100BT 12XDS1 100BT 41636000 25M0D7W
25 4-QAM 16DS1+100BT 16XDS1 100BT 41636000 25M0D7W
25 8-PSK DS3+100BT DS3 100BT 62358000 25M0D7W
28 4-QAM 24DS1 16XDS1 8XDS1 46500000 27M5D7W
28 8-PSK 28DS1 16XDS1 12XDS1 69750000 27M5D7W
28 8-PSK 32DS1 16XDS1 16XDS1 69990000 27M5D7W
Table F-B Frequency Licensing Data; All Data Rates & LIM Profile (continued)
BW (MHz) MOD Data Rate LIM A LIM B Aggregate Rate (bps) Emission Designator
28 8-PSK DS3 DS3 69750000 27M5D7W
28 8-PSK DS3+2DS1 2XDS1 DS3 69750000 27M5D7W
28 8-PSK DS3+4DS1 4XDS1 DS3 69333999 27M5D7W
28 8-PSK DS3+8DS1 8XDS1 DS3 69750000 27M5D7W
28 8-PSK DS3+12DS1 12XDS1 DS3 69846000 27M5D7W
28 16-QAM DS3+16DS1 16XDS1 DS3 93000000 27M5D7W
28 32-QAM 2xDS3 DS3 DS3 116250000 27M5D7W
28 32-QAM 2DS1+100BT 2XDS1 100BT 116660000 27M5D7W
28 32-QAM 4DS1+100BT 4XDS1 100BT 116660000 27M5D7W
28 32-QAM 8DS1+100BT 8XDS1 100BT 116660000 27M5D7W
28 32-QAM 12DS1+100BT 12XDS1 100BT 116660000 27M5D7W
28 32-QAM 16DS1+100BT 16XDS1 100BT 116660000 27M5D7W
28 32-QAM DS3+100BT DS3 100BT 116660000 27M5D7W
28 4-QAM 2DS1+100BT 2XDS1 100BT 46564000 27M5D7W
28 4-QAM 4DS1+100BT 4XDS1 100BT 46564000 27M5D7W
28 4-QAM 8DS1+100BT 8XDS1 100BT 46564000 27M5D7W
28 4-QAM 12DS1+100BT 12XDS1 100BT 46564000 27M5D7W
28 4-QAM 16DS1+100BT 16XDS1 100BT 46564000 27M5D7W
28 8-PSK DS3+100BT DS3 100BT 69846000 27M5D7W
28 4-QAM 16E1 8XE1 8XE1 46200000 27M5D7W
28 4-QAM 8XE1 8XDS1 46564000 27M5D7W
28 8-PSK 16XE1 16XDS1 69846000 27M5D7W
28 8-PSK DS3+2DS1 2XE1 DS3 69846000 27M5D7W
28 8-PSK DS3+4DS1 4XE1 DS3 61350000 27M5D7W
28 8-PSK DS3+8DS1 8XE1 DS3 69846000 27M5D7W
28 16-QAM DS3+16DS1 16XE1 DS3 93304000 27M5D7W
28 16-QAM E3 DS3 93304000 27M5D7W
28 4-QAM 16XE1 46200000 27M5D7W
28 4-QAM 16XE1 46200000 27M5D7W
28 4-QAM 20E1 16XE1 4XE1 46200000 27M5D7W
28 4-QAM 4XE1 16XE1 46200000 27M5D7W
28 8-PSK 24E1 16XE1 8XE1 68840001 27M5D7W
28 8-PSK 8XE1 16XE1 68844000 27M5D7W
28 16-QAM 32E1 16XE1 16XE1 91680000 27M5D7W
28 16-QAM E3+16E1 16XE1 E3 91680000 27M5D7W
28 16-QAM E3 16XE1 91680000 27M5D7W
28 4-QAM E3 E3 46056000 27M5D7W
28 4-QAM E3 46056000 27M5D7W
28 4-QAM E3+4E1 4XE1 E3 46584000 27M5D7W
28 16-QAM E3 E3 91680000 27M5D7W
28 8-PSK E3+8E1 8XE1 E3 69300000 27M5D7W
28 4-QAM 100BT 100BT 46564000 27M5D7W
28 4-QAM 100BT 100BT 46564000 27M5D7W
28 32-QAM 100BT 115700000 27M5D7W
28 32-QAM 100BT 100BT 115700000 27M5D7W
28 4-QAM 2E1+100BT 2XE1 100BT 46564000 27M5D7W
28 32-QAM 2XE1 100BT 116430000 27M5D7W
28 32-QAM 4E1+100BT 4XE1 100BT 116180000 27M5D7W
28 4-QAM 4XE1 100BT 46564000 27M5D7W
28 32-QAM 8E1+100BT 8XE1 100BT 116180000 27M5D7W
28 4-QAM 8XE1 100BT 46564000 27M5D7W
Table F-B Frequency Licensing Data; All Data Rates & LIM Profile (continued)
BW (MHz) MOD Data Rate LIM A LIM B Aggregate Rate (bps) Emission Designator
28 4-QAM 12E1+100BT 12XE1 100BT 46564000 27M5D7W
28 32-QAM 12XE1 100BT 115700000 27M5D7W
28 32-QAM 16E1+100BT 16XE1 100BT 115700000 27M5D7W
28 4-QAM 16XE1 100BT 46564000 27M5D7W
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 G-A and Figure G-1, to mount a
of vendors that use a non-protected or 1+1 protected RF unit on a pole separate from an an-
standard rectangular tenna that uses a standard waveguide feed. Employ the offset ODU op-
waveguide interface. tion where a Proteus AMT push-fit antenna is not available, a site has an-
tennas 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 G-A ODU - RFU Offset Mounting Kit
Description P/N
7/8-GHz ODU Offset Mounting Kit, Circular I/O 8708271-07
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 G-B lists components of the ODU offset kit. Table G-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 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 G-E lists components of the ODU rack mounting kit. Table G-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 G-2 shows hardware placement.
Step 2: Use #4-40 screws to secure the mounting bracket (Figure G-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 G-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
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 G-H lists some of the flexible waveguide available for use with the
ODU offset mounting option. Contact MNI sales for different lengths.