GE MDS LEDR400S-74 Users Manual
8.0 UPGRADING LEDR FIRMWARE
8.1 Introduction
The LEDR radio’s firmware can be upgraded with new software
releases that may be issued from time-to-time by Microwave Data Systems. To support firmware upgrades while the radio is in use, the LEDR
radio contains two complete copies of its firmware. Once the inactive
version is replaced, the radio can be rebooted using the code in the new
firmware. However, if an error occurs during the download, the radio
can easily recover because it always has a complete copy of firmware
available.
Reprogramming can be done through three common options:
1. Locally through the front panel
2. Locally using TFTP and Telnet through the
3. Remotely over a network connection using TFTP and Telnet to the
ETHERNET Port .
The procedures that follow use one or both of two utilities found in
MDS’ LEDR Utilities package. These utilities will facilitate local and
remote transferring of firmware files to and from the LEDR radio. These
applications are available from Microwav e Data Systems on floppy disk
(P/N 03-3631A01) or on MDS’ Internet sites FTP section of the primary
site of www.microwavedata.com.
The following sections will explain how to program new firmware into
the radio using each of the three connection options. They assume the
LEDR Utilities are installed on each computer system named in the procedure.
NOTE: The ETHERNET, SERVICE CHANNEL and CONSOLE Ports
share a common data channel when loading firmware
over-the-air. Transferring the radio firmware image file (≈ 1
MB), may take up to 30 minutes if there is other activity on any
of the other ports.
CONSOLE Port .
ETHERNET Port .
Regardless of your connection to the LEDR radio, loading
data/firmware into the radio’s SRAM is much slower than
loading software onto a PC hard drive or RAM.
MDS 05-3627A01, Rev. C LEDR Series Installation & Operation Guide 93
8.2 OPTION 1: Uploading Firmware via the
This method of upgrading the firmware is well suited to field service
personnel that carry a laptop PC to field installation. Any computer running the Windows operating system is suitable. Figure 17 shows the
basic arrangement.
FLASH
UTILITY
INITIATE UPLOAD
FROM HERE
Figure 17. Direct connection through the LEDR CONSOLE Port
CONSOLE Port
Invisible place holder
LEDR RADIO UNITWINDOWS PC
9-PIN SERIAL CABLE
COM1, 2, ETC.
(DTE)
CONSOLE PORT
(DCE)
Setup
Connect a PC to the radio’s front panel
CONSOLE Port using a 9-pin
RS-232 cable. (See Figure 33 on Page 129 for cable wiring details.) The
CONSOLE Port supports RS-232 at 9600 bps to 38.4 kbps.
Download Procedure
1. Start the MDS MDS Flash Utility application.
2. From the
baud rate. Ensure that
View>Options menu, select the appropriate COM Port and
autobaud is enabled (Look in the lower
right-hand corner of the Flash Utility window).
3. From the
dow to the LEDR radio. At the
View menu, select console. This will bring up a NMS win-
LEDR> prompt, enter a login name
and password and then close the session.
4. Using the
ware is located. In the file window, highlight the correct (
and then press the green
File|Open dialog, select the directory where the new firm-
.mpk) file
start arrow.
94 LEDR Series Installation & Operation Guide MDS 05-3627A01, Rev. C
Verification and Reboot
1. To verify the correct operation of the new firmware, open the NMS
again by pressing
Alt + L. Enter boot to determine which image is
currently active. This command will respond as follows:
boot: Image 1 is Active or, boot: Image 2 is Active
2. The new firmware is do wnloaded into the inactive image. Therefore,
if the radio responded
mand,
iverify 2, otherwise, enter iverify 1. The radio will respond indi-
Image 1 is Active, enter “image verify” com-
cating whether or not the image has been verified as being a valid
file, it will not determine if the contents are complementary to the
other firmware image. If the image does not verify, try downloading
the firmware again into the radio.
NOTE: The following paragraph describes rebooting the radio. This
action will disrupt the communications link.
3. Once the image has been verified, the radio must be rebooted using
the new firmware. This is done by entering the command
boot 2, where the 1 or 2 corresponds with the image number used
with the
iverify command above.
boot 1 or
4. Once the radio has rebooted and Flash Utility screen displays the
LEDR> prompt, the firmware can be downloaded or copied into the
other image. Often, copying the firmware from one image to the
other can be faster than performing a second download. To copy the
firmware over to the other image, simply enter
prompt you for confirmation (
y/n) and then begin copying.
icopy. The radio will
8.3 OPTION 2: Uploading Firmware Locally by
Telnet via Ethernet
This method can be used in the field or in a workshop by using a Windows computer equipped with an Ethernet interface. Figure 17 shows
the basic arrangement.
NOTE: You must know the IP address of the LEDR Radio and the PC
that you are going to connect together. (Both units must have
the same Subnet, Netmask and Gateway addresses, or at least
have routes to one another.) This is essential for a direct
Ethernet connection.
If you do not know your Windows computer’s IP address, you
can use the RUN function from the Start menu and enter winipcfg
to determine your local PC’s IP address. The IP address of the
radio can be found by the use of the radio’s ip command.
MDS 05-3627A01, Rev. C LEDR Series Installation & Operation Guide 95
LOCAL WINDOWS PC
W/FIRMWARE FILES
TFTP
SERVER
& TELNET
IP ADDRESS: 192.168.X.B
INITIATE UPLOAD
FROM HERE
LEDR> REPROGRAM NETWORK FILENAME.MPK 192.168.X.B
(CHECK STATUS: LEDR> REPROGRAM STATUS)
ETHERNET
PORT
CROSS-OVER CABLE
Figure 18. Direct connection through the LEDR ETHERNET Port
Setup
Invisible place holder
ETHERNET
PORT
LEDR RADIO UNIT
IP ADDRESS: 192.168.X.W
1. Connect the PC’s Ethernet interface to the radio’s
ETHERNET Port
using a Category 5 Ethernet cross-over cable.
2. Copy the file LEDR firmware image file (
directory on your PC. For example,
ledr.mpk) into a known
c:\windows\LEDR\Firmware V2.5\.
This directory path will be used later by the TFTP server.
Download Procedure
1. Launch the MDS TFTP Server on a PC connected to the LEDR
radio’s
ETHERNET Port through a cross-connect cable.
2. Point the TFTP server to the directory from which you desire to
upload the new firmware. In the SNMP TFTP server, you should
execute the
where
set root command and point to the known directory
ledr.mpk has been copied.
3. Launch your Telnet application and login to the radio which you
desire to load (reprogram) the firmware image file.
4. Determine the active (firmware) image from which you are currently
executing by typing
boot. The new firmware will downloaded into
the inactive image.
5. Execute the command
command, in place of
address of the TFTP server. For example,
192.168.1.2
reprogram network ledr.mpk [IP address]. In the
[IP address], you should actually type the IP
reprogram network ledr.mpk
96 LEDR Series Installation & Operation Guide MDS 05-3627A01, Rev. C
6. If desired, the status of the transfer during reprogramming may be
displayed by typing
reprogram status.
7. The TFTP Server and radio will notify you when the programming
is complete.
Verification and Reboot
1. To verify the integrity of the new firmware enter
boot to determine
which image is currently active. This command will respond as
follows:
boot: Image 1 is Active or, boot: Image 2 is Active
If the radio responded to the boot command with Image 1 is Active,
enter the “image verify” command,
iverify 1. The radio will respond indicating whether or not the image
iverify 2, otherwise, enter
has been verified as being a valid file, it will not determine if the
contents are complementary to the other firmware image. If the
image does not verify, try downloading the firmware again into the
radio.
NOTE: The following paragraph describes rebooting the radio. This
action will disrupt the communications link.
2. Once the image has been verified, the radio must be rebooted using
the new firmware. This is done by entering the command
boot 2, where the 1 or 2 corresponds with the image number used
with the
iverify command above.
boot 1 or
3. Once the radio has rebooted and Flash Utility screen displays the
LEDR> prompt, the firmware can be downloaded or copied into the
other image. Often, copying the firmware from one image to the
other can be faster than performing a second download. To copy the
firmware over to the other image, simply enter
prompt you for confirmation (
y/n) and then begin copying.
icopy. The radio will
8.4 OPTION 3: Uploading Firmware from a Remote
Server via Ethernet
Setup
Connect the LEDR radio’s ETHERNET connector to network which has
a PC connected with the desired LEDR firmware on its hard drive. The
“network” can be a local area network, a wide-area network or any IP
network that can connect the two units.
MDS 05-3627A01, Rev. C LEDR Series Installation & Operation Guide 97
The computer hosting the firmware image, must be running a TFTP
server software. If not, install, launch and configure the MDS TFTP
Server software found on the LEDR Utilities disk. The setup configura-
tion is shown in Figure 19.
REMOTE PC
W/FIRMWARE FILES
TFTP
SERVER
ETHERNET
PORT
IP ADDRESS: 192.168.X.B
Invisible place holder
HUB/LAN/WAN/MAN
TCP/IP
ETHERNET
PORT
LOCAL WINDOWS PC
TERM
PROG.
INITIATE UPLOAD
FROM HERE
COM1, 2, ETC.
(DTE)
LEDR> REPROGRAM NETWORK FILENAME.MPK 192.168.X.B
(CHECK STATUS: LEDR> REPROGRAM STATUS)
CONSOLE PORT
(DCE)
9-PIN SERIAL
CABLE
LEDR RADIO UNIT
IP ADDRESS: 192.168.X.W
Figure 19. Uploading firmware from a remote server via Ethernet
Download Procedure
1. Start a terminal program, such as HyperTerminal, on the local PC.
2. Log into the LEDR radio using the login command.
3. Use the ip command to ensure that the radio has a valid IP address.
4. Use the ping command from the local PC to ensure that the PC and
the radio have valid routes to pass information between them.
5. At the radio’s
gram network
monitored from the radio by entering
LEDR> prompt, start the download by entering repro-
[filename] [source PC’s IP Address]. The download can be
reprogram status. When the
download is complete the radio will sound two short beeps and the
response from
reprogram status will indicate that the download has
finished.
98 LEDR Series Installation & Operation Guide MDS 05-3627A01, Rev. C
SNMP Option The TFTP download process can also be initiated using an SNMP man-
ager. The
Firmware|FwProgTable object provides a means for specifying
the TFTP server IP address and the filename for the firmware.
Verification and Reboot
When the download is complete, verify the firmware image and reboot
the radio as described under Verification and Reboot in Paragraph See
“Verification and Reboot” on Page 95 for the procedure.
9.0 USING ORDERWIRE
9.1 Introduction
A handset may be plugged into the front panel of the LEDR radio to
allow voice communications between radio sites (see Figure 20). This
can be especially useful during setup and service of the radio equipment.
All radios on the network can hear what is said by any individual
speaking into a handset. No other radio may transmit on the orderwire
until the current speaker is finished. Depending on the number of hops,
the link data rates, and Interleave setting, there may be a noticeable
latency from one end of the network to the other.
The front panel alert function (See “Unit ID” on Page 34) and
alert com-
mand (Page 51) can be used to signal all units in the network or a specific radio.
Normal payload data is not affected by Orderwire use. The Orderwire
uses voice-compression technology that introduces a slight, but noticeable, delay in Orderwire audio.
The orderwire will not interrupt the normal data flow through the LEDR
data communication channel, however, it will reduce the throughput
efficiency of any data communications on the Service Channel during
periods of voice transmission.
A handset is available from MDS (P/N 12-1307A01), which has a
push-to-talk button and provides basic communication services but does
not contain a built-in DTMF (tone) keypad. (The Orderwire supports the
transmission of DTMF-type signaling by detecting tones at the source,
and regenerating them at the receiving end, however, there are no
DTMF supported radio functions in the LEDR radios.)
9.2 Setup
Program the vox and volume setting for each radio. The volume setting is
user preference. The
the
vox setting, the louder the user must speak to get the voice decoder
to recognize the speech. This will, however, prevent noise from entering
vox setting requires some forethought. The higher
MDS 05-3627A01, Rev. C LEDR Series Installation & Operation Guide 99
the “line.” A low vox level will recognize speech better but may transmit
more noise with the speech. The user should experiment with the
vox
setting to determine the best level for the speaker and the noise environment.
9.3 Operation
1. Plug the handset into the front panel jack labeled . (Figure 32
on Page 129 provides pinout details for this connector.)
2. Press or at the menu’s top level until Orderwire appears on
ENTER
the LCD display . Press
3. To call a specific radio station, enter the Unit ID number for the station to be called. (At this point, an alert signal (“ring”) will be sent
to earpiece of the handset connected to the “called” station.
4. Press the PTT on handset to speak to the other station(s) listening to
their handsets connected to LEDR equipment on the network.
Release the handset PTT to listen. VOX (voice-activated transmit)
operation is also supported. (See “vox” on Page 88.)
to move to the lower levels of the menu.
5. Alternatively, a DTMF-style handset can be used to “dial” the
required radio station.
6. Remember, regardless of the number of users, only one may speak
at a time.
NOTE: The LEDR radio has a built-in DTMF decoder in the orderwire
circuitry. If a standard DTMF telephone test set is plugged into
the orderwire, the user can dial in the three digit unit address
on the handset to “ring” the earpiece of the handset of the associated LEDR unit.The LEDR chassis will not provide power to
ring a standard bell or electronic ringer.
100 LEDR Series Installation & Operation Guide MDS 05-3627A01, Rev. C
Invisible place holder
Figure 20. Orderwire Connection
9.4 Related NMS Commands
The orderwire can be configured by the NMS commands or through the
front panel. The earpiece volume is more easily set by the front panel
controls as the level is dependent on personal preference.
vox – Voice level (relative) at which speech will be detected by the soft-
ware (See “vox” on Page 88)
volume – Sets/displays the handset volume (See “volume” on Page 88)
alert – Sends an orderwire alert to a specific radio or to all the radios on
the network (See “alert” on Page 51)
10.0 USING THE SERVICE CHANNEL
10.1 Concept
The Service Channel sends and receives ASCII-based information at
9600 bps in a half-duplex broadcast mode throughout the network. This
means that any data coming through the Service Channel Port of a radio
will be broadcast to the Service Channel of each radio in the network.
There can be only one radio transmitting Service Channel data over the
network at a time and the data will always be sent to every radio on the
network. No other radio will be allowed to transmit until the current
sender is finished.
MDS 05-3627A01, Rev. C LEDR Series Installation & Operation Guide 101
If a radio does receive data in the Service Channel Port while another
radio is the active-sender, the data coming in the port will be queued and
sent when the active sender is finished. Depending on the number of
hops, link data rate, and Interleave setting, there may be a noticeable
latency from one end of the network to the other.
10.2 Setup
The user can configure all the Service Channel parameters for a specific
radio. The port may be enabled or disabled. In the disabled state (
port off
), any data that comes in the Service Channel port will be discarded and any Service Channel data that comes into the radio from
another radio in the network will be passed along to the rest of the network but not sent out the Service Channel Port. When the Service
Channel Port (
svch port on) is enabled, it will behave based on the other
settings.
The most important setting is the echo parameter. Echo is used with a
terminal emulator on a PC and the program does not display on the
screen character keyed in by the user.
svch
When you set up a system, you must be careful to avoid an infinite loop.
If echo is enabled, then every character that enters the Service Channel
port will be echoed back out the port. When echo is disabled then data
that comes in the Service Channel port is not sent back out the port.
Trouble may arise if the device that is connected to the Service Channel
also echoes the data it sends. In that case, the device will send characters
into the Service Channel Port, the radio will echo the characters back to
the device, the device will consider the echoed data to be input which it
will in turn echo back to the radio, etcetera, until an overflow condition
occurs.
You must also set the communication parameters (baud rate, stop bits,
char length, and parity) via the
svch subcommands so that the settings
match those at the device connected to the Service Channel Port.
Lastly, the user can re-initialize the Service Channel port via the svch
command. This may be helpful in the case where an infinite loop
reset
overflow condition has locked the port.
10.3 Usage
The Service Channel supports ASCII data transfer over the network in
broadcast fashion. As a result, devices connected to the Service Channel
Ports of different radios will appear to have a transparent half-duplex
connection between them.
102 LEDR Series Installation & Operation Guide MDS 05-3627A01, Rev. C
10.4 NMS Commands
This command is used to set/display Service Channel parameters.
Usage:
svch [subcommand] [<argument>]
Subcommands:
on
—Enable the Service Channel
off—Disable the Service Channel
reset—Re-initialize the Service Channel
echo—on/off
baud—300, 600, 1200, 2400, 4800 and 9600
char— 5, 6, 7, 8 (ASCII character length in bits)
parity—none, even, odd
stop—1, 2 (Stop bits)
baud
char
echo
off
off
on
parity
reset
stop
11.0 PROTECTED CONFIGURATION
11.1 Introduction
The LEDR radio can be supplied in a protected (also called redundant
or “1+1”) configuration (Figure 21). The protected version is designed
to perform automatic switchover to a second radio in the event of a
failure in the primary unit.
Protected operation is important for many mission-critical or revenue
producing links. By configuring two identical LEDR radios in parallel
and including a third switch box containing the RF switching circuits
and the customer interfaces, it is possible to protect against failure in any
of the LEDR radio sub-systems. Failures can be either malfunction or
external environmental effects, such as multipath fading or nearby lightning strikes.
A Protected station consists of two standard LEDR Series radios and a
Protected Switch Chassis (center unit in Figure 21). Ordinarily, the three
chassis are mounted together in a “stacked” arrangement, one above the
other, as shown in the figure.
MDS 05-3627A01, Rev. C LEDR Series Installation & Operation Guide 103
The top unit is referred to as the system’s “Unit A”, and the lower one
as “Unit B”. Each unit is considered to be the “sibling” of the other. The
sibling of Unit A is Unit B, and the sibling of Unit B is Unit A. This distinction is used in the
rdnt command found on Page 74 under the sub-
heading “Read & Write Commands.”
Invisible place holder
UNIT A
PSC
UNIT B
Figure 21. LEDR Radio Protected Version
The front panel of the Protected Switch Chassis (PSC) front panel has
only two LEDs and an RJ-45 jack for an orderwire handset. The LEDs
indicate by light and an arrow outline which LEDR chassis is active. It
is assumed the two LEDR chassis will be mounted above and below the
PSC as shown in Figure 21.
11.2 Protected Operation
During normal operation, one radio path is selected and the RF and
interface switches are set to service that path. (The illuminated
LED indicator on the front panel of the Protected Switch Chassis (PSC)
points to the currently active unit.) A switch in the transmitter circuitry
allows one transmitter to be connected to the common
ANTENNA port on
the Protected Switch Chassis. On the receive path, a splitter in the Protected Switch Chassis allows both radio receivers to receive the
incoming RF signal for processing.
The Protected Switch Chassis is a gateway for data coming and going
between each of the LEDR radio units and the common data circuits
connected to the PSC. The PSC monitors various RF and data signal
paths for predefined fault-determining parameters. If signal conditions
are not normal, the PSC’s microprocessor controller will issue an alarm
and move the standby LEDR radio to the active mode.
POWER
104 LEDR Series Installation & Operation Guide MDS 05-3627A01, Rev. C
Fault-determining parameters can be programmed from the Network
Management System (NMS) software. Examples of these parameters
are:
• Low transmitter power
• High transmitter temperature
• Synthesizers is out-of-lock
• Problem with the option board or framers
• CPU failure wherein the CPU watchdog causes a reset
• Fan fault
Transmitter Failure
Any failure on the “active” transmitter path will create a fault condition
which will place the currently the active transmitter on standby and
switch the “standby” transmitter to “active.” The newly active transmit
path will remain in use until a manual changeover returns the configuration to the original transmitter path. This allows the link to remain
fully operational until the user has replaced the faulty transmitter circuitry.
Receiver Failure
Both receivers are fed via an RF splitter from the antenna port. Each RF
path is buffered and monitored for receive signal integrity for uncorrectable bit-errors. If the “active” receive circuitry fails, uncorrectable
bit-errors will be detected. The modem receive switch will first determine that the “standby” receive path is operational (no uncorrectable bit
errors) and will switch accordingly.
11.3 Configuration Options
The protected LEDR radio is available with a number of configuration
options, each designed to optimize particular system solutions:
1+1 Operation—Warm or Hot Standby
In a warm standby link, the standby transmitter is powered down. In a
hot standby link, the standby transmitter is powered up and transmitted
in a dummy load. The warm standby option offers the advantages of significantly reduced power consumption, since only one transmitter path
is powered. However, upon transmitter failure, the switchover takes
longer due to the transmitter having to be powered. Thus the hot standby
mode offers the advantages of faster switchover time and increased
overall system availability.
MDS 05-3627A01, Rev. C LEDR Series Installation & Operation Guide 105
Symmetrical or Asymmetrical Receiver Splitters
The default protected radio is configured with a 3 dB splitter on the
receive path, meaning that each radio’s receiver signal level is equal, but
typically 4dB worse than an unprotected radio (3 dB due to splitter, plus
dB cabling and additional connectors). As an option, an asymmetrical
splitter (1 dB / 10 dB) is offered. Using this option, the active path is 2
dB stronger than with a symmetrical splitter (1 dB compared to 3 dB
splitter loss), allowing for a better fade margin and increased system
availability during normal operation.
However, upon receiver change over, the receive signal strength will be
significantly reduced due to the 10 dB of splitter loss rather than the
equal splitter’s 3 dB loss, making the link more sensitive to fading in this
temporary switched state. Providing the failed standby receiver is
replaced within a short period of time, many users find that the asymmetric splitter’s increased normal performance offsets any deterioration
in the temporary switched state.
11.4 PSC Rear Panel Connectors
The following are descriptions of the rear panel connections of the Protected Switch Chassis. The PSC’s rear chassis is shown in Figure 22.
RF CONNECTORS
Figure 21 presents an inter-unit cabling diagram for protected configu-
rations.
Invisible place holder
PROTECTED DATA
A
B
TxBAntenna TxARxBRxA
E1 DATA
ETHERNET
12
34
530 (A&B)
530 (A&B)
Figure 22. Protected Switch Chassis—Rear Panel
EIA-530-A
SERVICE CHANNEL
EIA-530-A Service ChannelEthernetE1Protected
RxA
The RXA (Receive—Radio A) connector is a N-type coaxial connector.
It connects to the
RX port on the rear panel of Radio A via a short coaxial
cable.
RxB
Same as
RXA, but for Radio B.
Antenna
The
ANTENNA connector is a N-type coaxial connector. It serves as the
connection point for the station antenna.
106 LEDR Series Installation & Operation Guide MDS 05-3627A01, Rev. C
TxA
The
TXA (transmit, radio A) connector is a N-type coaxial connector. It
connects to the
TX port on the rear panel of Radio A via a short coaxial
cable.
TxB
Same as
TXA, but for Radio B.
Protected (Data)
This pair of connectors accepts G.703 signals from each of the LEDR
radios. The top connector is for Radio A, and the bottom connector is for
Radio B. For pinout information, see Figure 36 on Page 130.
E1
This is a block of four RJ-45 modular connectors for connection to a
multiplexer or other customer-supplied E1 equipment. For detailed pin
information, Figure 34 on Page 130.
These connectors are not operational on “S” Series (Subrate) radios.
Ethernet
The
ETHERNET connector provides access to the embedded SNMP
agent and other elements of the TCP/IP network management system.
The connector is a standard 10 Base-T connection with an RJ-45 modular connector. For detailed pin information, see Figure 34 on Page 130.
530 (A&B)
This pair of DB-25 connectors accepts EIA-530 data signals from each
of the LEDR radios. The top connector is for Radio A, and the bottom
connector is for Radio B. For pinout information, see Figure 36 on
Page 130.
EIA-530-A
This DB-25 connector provides a connection point for customer-supplied EIA-530 data equipment. Note: This port is not operational in fullrate models.
Service Channel
In a protected configuration, this DB-9 connector becomes the Service
Channel connection for both LEDR radios. (In the protected radio configuration, the Service Channel connectors on the radios are non-functional.) For detailed pin information, see “Service Channel—Rear
Panel” on Page 131.
MDS 05-3627A01, Rev. C LEDR Series Installation & Operation Guide 107
11.5 Inter-Unit Cabling for Protected Stations
The required cabling between the two radios and the Protected Switch
Chassis is dependent on the data interface, unit type (subrate versus
full-rate), and transmit and receive antenna configuration.
The cabling for a pair of standard radios with internal duplexers is
shown in Figure 23.
DO NOT USE IN
G.703/Expansion Data
PROTECTED CONFIG.
Ethernet
NMS
EIA-530-A
Service
Channel
Alarm I/O DC Power Input
RADIO A
RX
COAXIAL CABLES (4)
P/N 19-1323A02 CABLE 1A
RX
External
TO
STATION
ANTENNA
External
TX
P/N 03-3837A01
TxBAntenna TxARxBRxA
TX
Figure 23. Inter-unit Cabling—Protected Version
CABLE 1B
P/N 03-3837A01
G.703/Expansion Data
Data Interface
CABLE 2A
P/N 03-3828A01
(SUBRATE MODELS)
TO
MUX OR OTHER
E1 EQUIPMENT
12
34
TO ETHERNET HUB
CABLE 2B
P/N 03-3828A01
(SUBRATE MODELS)
Ethernet
NMS
Data Interface
PROTECTED CONFIG.
530 (A&B)
EIA-530-A
DO NOT USE IN
with Internal Duplexers
TO EIA-530
DATA EQUIPMENT
(SUBRATE MODELS)
PROTECTED SWITCH
EIA-530-A Service ChannelEthernetE1Protected
SERVICE CHANNEL
(SERVES BOTH RADIOS)
Service
Channel
Alarm I/O DC Power Input
RADIO B
11.6 Configuration Commands for a Protected
System
NOTE: In a protected link configuration, ensure that the E1/T1 inter-
face settings are identical for both radios at a each end of the
link.
Once the inner-chassis cabling is in place and the units are powered up,
several parameters are required to place the LEDR radio into proper
operation as a member of a protected system.
The tasks involved are reviewing and setting up of the following parameters:
108 LEDR Series Installation & Operation Guide MDS 05-3627A01, Rev. C
• Radio Operation
• General
• Redundant Specific
• Data Interface
• Subrate—Fractional-T1
• Fullrate—E1/T1
Redundant Specific Parameters
There are several parameters that must be set to enable proper operation
of a protected station. These are all covered under the
rdnt command
found on Page 74.
Sample Redundant Configuration Session
The following is a example of a session used to configure a LEDR radio
to serve in a protected system. This sequence will need to be repeated
for each radio in the protected pair.
1. Configure the protected mode to hot-standby:
LEDR> rdnt mode 1
rdnt {mode}: 1+1 Hot Standby
LEDR>
2. Configure the IP address of each radio:
LEDR> ip address 192.168.1.1
ip {netmask}: (255.255.0.0)
ip {gateway}: (0.0.0.0)
ip {port}: (ETH)
ip {address}: 192.168.1.1
ip {netmask}: 255.255.0.0
ip {gateway}: 0.0.0.0
ip {port}: ETH
ip: A reboot is strongly recommended. Do you wish to reboot? (y/n) >y
LEDR>
3. Configure the sibling IP address of each radio:
LEDR> rdnt ip 192.168.1.2
redundant {ip}: 192.168.1.2
LEDR>
4. Configure the hitless switching. (Note that the default is on.):
LEDR> rdnt hitless on
rdnt {hitless}: on
LEDR>
5. Configure the temperature (°C) threshold:
LEDR> rdnt temp 100
rdnt {temp}: 100
LEDR>
MDS 05-3627A01, Rev. C LEDR Series Installation & Operation Guide 109
Loading...