User's Manual
Table Of Contents
- 1.0 INTRODUCTION
- 2.0 MODEL NUMBER CODES
- 3.0 HARDWARE INSTALLATION AND BASIC INTERFACE REQUIREMENTS
- 4.0 INITIAL STARTUP AND CONFIGURATION
- 4.1 Introduction
- 4.2 STEP 1—Power up the LEDR Radios
- 4.3 STEP 2—Establish Communications with the Radio
- 4.4 STEP 3—Make Initial Login to Radio
- 4.5 STEP 4—Change the SUPER Password
- 4.6 STEP 5—Review Essential Operating Parameters
- 4.7 STEP 6—Set TCP/IP Settings to Enable SNMP and/or Telnet Management (if required)
- 4.8 STEP 7—Set User Configurable Fields
- 4.9 STEP 8—Verify Radio Performance
- 4.10 STEP 9—Install the Link
- 4.11 STEP 10—Verify the Link Performance
- 5.0 CONFIGURATION AND CONTROL VIA THE FRONT PANEL
- 6.0 CONFIGURATIONAND CONTROL VIA THE CONSOLE PORT
- 7.0 STANDARDIZING RADIO CONFIGURATIONS
- 8.0 UPGRADING LEDR FIRMWARE
- 9.0 USING ORDERWIRE
- 10.0 USING THE SERVICE CHANNEL
- 11.0 PROTECTED CONFIGURATION
- 12.0 SPACE DIVERSITY OPERATION
- 13.0 SPARE PARTS, UNITS AND ACCESSORIES
- 14.0 Fractional-T1 INTERFACE CARD 03-3846A01 Fractional-E1 INTERFACE CARD 03-3846A02
- 15.0 INCREASE BANDWIDTH BY CHANGING TRANSMITTER AND RECEIVER FILTERS
- 16.0 BENCH TESTING OF RADIOS
- 17.0 TECHNICAL REFERENCE
- 17.1 Specifications— Models: LEDR 400S, 700S, 900S and1400S
- 17.2 Specifications— Models: LEDR 400F, 900F, 1400F
- 17.3 Specifications— Protected Switch Chassis
- 17.4 Optional Equipment (Consult factory for detailed information)
- 17.5 Accessories
- 17.6 I/O Connector Pinout Information
- 17.7 Watts-dBm-Volts Conversion
- 18.0 RADIO EVENT CODES
- 19.0 IN CASE OF DIFFICULTY
MDS 05-3627A01, Rev. D LEDR Series I/O Guide 79
Background on this command:
The LEDR Series of radios can be configured to pass IP management
traffic across the radio’s raw service channel. A process called “network
self-discovery” automatically configures IP routes between all radios in
a network (provided that the
group command has been correctly config-
ured throughout the system. (See “group” on Page 60). Also, see the arp
command on Page 51.
IP management traffic routing allows configuring and monitoring
devices other than LEDR radios using the same management channel,
providing clean integration of SNMP, Telnet, TFTP, and other IP man-
agement methods via one channel that doesn’t use any of the customer
payload bandwidth of the radio network.
Routes must be added to the radios at two points in the system to support
routing IP traffic to and from the connected devices: 1. At the gateway
end (where the management station is located), and 2. At the destination
end. Routes are added to the radios using the same convention as used
in the MS Windows, Windows NT, and DOS operating environments.
The exceptions here are that a mask and port must be specified, as well
as the target and gateway IP addresses. At both ends, the command used
is exactly the same (see command Example 1, above). In the command
example given above, the route is being added at the gateway end. The
difference is that at the gateway end, the port is
air, and at the destination
end, the port is
eth. Routes do not need to be added at points between the
gateway and destination, because the radio network handles the routing
between radios via network self-discovery. However, in each radio, the
IP gateway must be specified as the IP address of the radio at the net-
work-management gateway in the system.
NOTE: Gateway Settings in Connected Devices
In the connected IP-manageable device, use the local radio’s
IP address as the default IP gateway for the device.
NOTE: Routing in Protected Systems
Each route added to a protected radio must be added to both
units in the protected pair, as they are stored separately. The
radios in a protected pair proxy for one another depending on
which radio is active, so the routing functionality is unchanged
and either radio in a protected pair can be specified as the
gateway for a connected device; but if a protected LEDR radio
is removed for servicing, all the routing information must be
programmed in the remaining radio for proper IP management
functionality.
rssi Received Signal Strength Indicator
Usage:
rssi