GE MDS DS-MERCURY900 User Manual

PRODUCT OVERVIEW
1
1 Chapter Counter Reset Paragraph
Contents
1.1 ABOUT THIS MANUAL ........................................................... 3
1.2 PRODUCT DESCRIPTION ..................................................... 4
AND APPLICATIONS
1.1.1 Start-Up Guide ......................................................................... 3
1.1.2 Online Access to Manuals ........................................................ 3
1.1.3 Conventions Used in This Manual ........................................... 3
1.2.1 Model Offerings ........................................................................ 6
1.2.2 MDS P23 Protected Network (Redundant) Configuration ........ 7
1.3 APPLICATIONS ....................................................................... 7
1.3.1 Mobile/Fixed Data System ....................................................... 7
1.3.2 Wireless LAN ........................................................................... 8
1.3.3 Point-to-Point LAN Extension .................................................. 9
1.3.4 Serial Radio Network Connectivity
(Future Functionality) .......................................................................... 9
1.3.5 Multiple Protocols and/or Services
(Future Functionality) .......................................................................... 10
1.3.6 Wireless LAN with Mixed Services ........................................... 10
1.3.7 Upgrading Older Wireless Network with
Serial Interfaces (Future Functionality) ............................................... 11
1.4 NETWORK DESIGN CONSIDERATIONS .............................. 12
1.4.1 Extending Network Coverage with Repeaters ......................... 12
1.4.2 Protected Network Operation using Multiple Access Points .... 14
1.4.3 Collocating Multiple Radio Networks ....................................... 15
1.5 GE MDS CYBER SECURITY SUITE ...................................... 16
1.6 ACCESSORIES....................................................................... 17
05-4446A01, Rev. A Mercury Reference Manual 1
2 Mercury Reference Manual 05-4446A01, Rev. A
1.1 ABOUT THIS MANUAL
This Reference Manual is one of two publications provided for users of the Mercury 900 information, an overview of common applications, a screen-by-screen review of the menu system, technical specifications, suggested settings for various scenarios, and detailed troubleshooting information. This manual should be available to all personnel who are responsible for net­work design, setup, commissioning and troubleshooting.
1.1.1 Start-Up Guide
The Mercury 900 Start-Up Guide (Part No. 05-4558A01) is a com­panion publication to the Reference Manual. It is a much smaller book, with a specific purpose—to guide an Installer in the basic steps for get­ting a transceiver on the air and communicating with other units in a net­work. It eliminates non-essential information so that installers can focus on the immediate goal of getting their equipment up and running in the shortest time possible.
TM
transceiver system. It contains detailed product
1.1.2 Online Access to Manuals
In addition to printed manuals, many users value the ability to access documents electronically. This can be especially useful when you need to access documentation while traveling, or want to share a document with another user in the field. Electronic documents also make it easy to search for a specific term or subject, especially in larger manuals.
User manuals for our equipment can be accessed anytime from our web­site at
www.GEmds.com . Simply click the
the home page and select
Product Manuals
Downloads
tab at the top of
from the drop-down list. A
search window then appears to help you locate the manual you need.
Online manuals are provided as PDF files in the Adobe
®
Acrobat
®
stan-
dard. A reader for PDF files may be downloaded free of charge from
www.adobe.com .
1.1.3 Conventions Used in This Manual
On-Screen Menu Items
On-screen menu items or command entries are presented in a distinctive typeface to set them apart from regular text (for example:
IP Address, Password
). This typeface will be found most often in Chapter 3, where the menu system is discussed in detail. When variable settings or a range of options are available for a menu option, the items are pre­sented inside brackets, with the default setting (if any) shown last, fol­lowing a semicolon.
Network Name,
Here is an example: [
05-4446A01, Rev. A Mercury Reference Manual 3
available settings or range;
default setting
]
Menu Strings
To help show the path to a menu selection, navigation strings are used in several places in this manual. For example, suppose you wished to view or set the Network Name assigned to your system. This item is located in the Network Configuration Menu, so the navigation string in the text would appear as follows:
Main Menu>>Network Configuration>>Network Name
By following this order of menus, you will be able to quickly reach the desired menu.
1.2 PRODUCT DESCRIPTION
The GE MDS Mercury 900
TM
transceiver is an easy-to-install wireless solution offering extended range, secure operation, and at multi-megabit performance in a compact and rugged package. The transceiver is ide­ally suited for demanding applications in fixed or mobile environments, where reliability and range are paramount.
The transceivers are commonly used to convey text documents, graphics, email, video, voice over IP (VoIP), and a variety of other application data between mobile, fixed-point, and WAN/LAN-based entities.
Based on multi-carrier Orthogonal Frequency Division Multiplexing (OFDM), the transceiver features high speed/low latency, basic Quality of Service (QoS) for prioritizing traffic, Ethernet and serial encapsula­tion, and network roaming. It also provides enhanced security features including AES encryption and RADIUS authentication, making the Mercury system the best combination of security, range and speed of any industrial wireless solution on the market today.
Invisible place holder
TM
Transceiver
Rugged Packaging
Figure 1-1. The GE MDS
(Remote unit shown, AP is similar in appearance)
Mercury 900
The transceivers are housed in a compact and rugged die cast-aluminum case that need only be protected from direct exposure to the weather. This one enclosure contains all necessary components for radio opera-
4 Mercury Reference Manual 05-4446A01, Rev. A
tion and data communications. The only user-serviceable component inside the case is a fuse for the DC power input line.
Simple Installation
Secure Operation
Mercury Transceivers are designed for rapid and trouble-free installa­tion. For basic services, you simply connect the antennas (900 MHz and GPS, as required), connect your data equipment, apply primary power, set a few operating parameters, and you are done. No license is required for operation in the U.S.A., Canada, and many other countries. Check requirements for your region before placing the equipment in service.
Most installations employ an omni-directional antenna at the Access Point (AP) location and mobile stations. Fixed Remote stations often employ a directional antenna aimed at the AP. Regardless of the type used, antennas are a vital part of the system and must be chosen and installed correctly. Refer to
INSTALLATION PLANNING on Page 109
for guidance on choosing suitable antennas and installation sites.
Data network security is a vital issue in today's wireless world. The transceivers
provide multiple tools to help you build a network that min­imizes the risk of eavesdropping and unauthorized access. Some are in­herent in the radio's operation, such as the use of 900 MHz spread-spectrum transmissions; others include data encryption, en­abling/disabling remote access channels, and password protection.
Remember, security is not a one-step process that can simply be turned on and forgotten. It must be practiced and enforced at multiple levels, 24 hours-a-day and 7 days-a-week. See
SUITE”
on Page 16 for more information about the transceiver’s secu-
“GE MDS CYBER SECURITY
rity tools.
Robust Radio Operation
The transceivers are designed for operation in the license-free 900 MHz Industrial, Scientific, and Medical (ISM) band. They can provide reli­able communications over long distances, even in the presence of weak signals or interference.
Mobile range depends on many factors, including terrain, building den­sity, antenna gain, and speed of travel. The unit is designed for suc­cessful application in a variety of mobile environments, and offers the best combination of range, speed and robustness available in an indus­trial wireless package today. By using multiple Access Points, a network can be created that provides consistent, reliable coverage over a large metropolitan area. See
“SPECIFICATIONS” on Page 123 for more
information on transmission range.
Flexible Services
Users with a mix of equipment having Ethernet and serial data interfaces can accommodate this equipment through the use of a Remote Dual Gateway. This flexibility allows the transceiver to provide services in data networks that are being migrated from legacy serial/EIA-232-based hardware to the faster and more easily interfaced Ethernet world.
05-4446A01, Rev. A Mercury Reference Manual 5
Flexible Management
Configuration, commissioning, troubleshooting and other maintenance activities can be done locally or remotely. Four different modes of access are available: local RS-232 console terminal, local or remote IP access (via Telnet or SSH), web browser (HTTP, HTTPS), and SNMP (v1/v2/v3).
The text-based interfaces (RS-232 console, Telnet, and SSH) are imple­mented in the form of easy-to-follow menus, and the terminal server configuration includes a wizard to help you set up the units correctly.
Transceiver Features
The transceiver’s design makes the installation and configuration easy, while allowing for future changes.
• Industrial-Grade Product—Extended temperature range for trouble-free operation in extreme environments
• Robust Radio Communications—Designed to operate over long distances in dense, high-interference environments
• Robust Network Security—Prevents common attack schemes and hardware from gaining access or control of network. Com­mon attack events are logged and reported by alarms.
• High Speed—1.5 Mbps is over 100-times faster than 9.6 kbps radios.
• Plug-and-Play Connectivity—AP or Remote configuration requires minimal setup
• Built-in GPS Receiver—GPS technology is used for timing and location data. The only external equipment needed for this func­tionality is a GPS antenna (several types are available from GE MDS).
1.2.1 Model Offerings
The transceiver comes in two primary models—Access Point and Remote. Unique hardware is used for each of these models. Of the Remote radios, there are two sub-types available— and
Max Remote , both of which support Ethernet and serial services.
Table 1-1 summarizes the different interface abilities for each type of
radio.
Standard Remote
Table 1-1. Transceiver Models and Data Interface Services
Model Sub-Type
Access Point
Remote Ethernet Bridge Yes Yes No
NOTES
1. COM1 provides access to the embedded Management System on all units.
6 Mercury Reference Manual 05-4446A01, Rev. A
N/A Yes Yes No
Max Remote Yes Yes Yes
Ethernet/LAN
1
COM1
1
USB
Access Point or Remote?—Quick ID Tip
The outward appearance of AP and Remote radios is nearly identical, however, the hardware for each type is different and they are cahngeable. An quick way to identify them is to look at the gasket seal in the center of the radio case.
APs have a black gasket.
tifies it as an AP or Remote unit.
Remote units have yellow gaskets while
In addition, a label on the top each radio iden-
not inter-
1.2.2 MDS P23 Protected Network (Redundant) Configuration
For mission-critical applications, a Protected Network Station is also offered. This unit incorporates two transceivers, two power supplies, and a switchover logic board that automatically selects between Trans­ceiver A and Transceiver B as the active radio. Figure 1-2 shows a view of the protected chassis. For system-level information on this product, see MDS publication 05-4161A01.
Invisible place holder
Figure 1-2. MDS P23 Protected Network Station
(incorporates two Transceivers, with Automatic Switchover)
1.3 APPLICATIONS
The following sections provide illustrations of typical transceiver instal­lations. This is meant as an overview only. It is recommended that a net­work manager be involved in all installation planning activities.
1.3.1 Mobile/Fixed Data System
Mercury transceivers support high-speed data communications in a mobile environment. In this application, Remote radios “roam” between different Access Points, providing seamless transitions and continuous coverage throughout a municipal area. Figure 1-3 shows an example of an integrated system employing both mobile and fixed Mercury trans­ceivers.
05-4446A01, Rev. A Mercury Reference Manual 7
R
Invisible place holder
Figure 1-3. Integrated Mobile/Fixed Application
1.3.2 Wireless LAN
The wireless LAN is a common application of the transceiver. It consists of a central control station (Access Point) and one or more associated Remote units, as shown in Figure 1-4 on Page 8. A LAN provides com­munications between a central WAN/LAN and remote Ethernet seg­ments. The operation of the radio system is transparent to the computer equipment connected to the transceiver.
The Access Point is positioned at a location from which it can commu­nicate with all of the Remote units in the system. Commonly, this is a high location on top of a building or communications tower. Messages are exchanged at the Ethernet level. This includes all types of IP traffic.
A Remote transceiver can only talk over-the-air to an Access Point unit (AP). Peer-to-peer communications between Remotes can only take place indirectly via the AP. In the same fashion, an AP can only talk over-the-air to associated Remote units. Exception: Two APs can com­municate with each other “off-the-air” through their Ethernet connectors using a common LAN/WAN.
Remote
Remote
Invisible place holder
LAN
LAN
Access Point
emote
LAN
Remote
LAN
WAN/LAN
Figure 1-4. Typical Wireless LAN
8 Mercury Reference Manual 05-4446A01, Rev. A
1.3.3 Point-to-Point LAN Extension
A point-to-point configuration (Figure 1-5) is a simple arrangement consisting of an Access Point and a Remote unit. This provides a com­munications link for the transfer of data between two locations.
Invisible place holder
Access Point
LAN/WAN
Remote
LAN
Figure 1-5. Typical Point-to-Point Link
1.3.4 Serial Radio Network Connectivity
(Future Functionality)
An important design feature of the transceiver is to provide a path for serial devices to migrate to IP/Ethernet systems. Many radio networks in operation today still rely on serial networks at data rates of 9600 bps or less. These networks can use the transceiver as a means to continue using the serial service, while allowing the infrastructure to migrate to an IP format.
A Remote transceiver with its serial port connected to a GE MDS serial-based radio, such as MDS x790/x710, MDS TransNET and others, provides a path for bringing the data from the older radio into the IP/Ethernet environment of a Mercury-based system.
Invisible place holder
Serial
Serial Conn.
MDS 4710 Remote
Device
NETWORK
ROUTER
NMS Control
Point
HUB
ROUTER
SCADA Host
Modbus/IP
Access Point
Remote Serial
Remote Serial
Remote Serial
Serial Conn.
Serial Conn.
MDS 4790
Master
MDS 9790
Master
MDS 9810
MDS 4710 Remote
MDS 9710 Remote
MDS 9710 Remote
MDS 9810 Remote
Master
MDS 9810 Remote
Serial
Device
Serial
Device
Serial
Device
Serial
Device
Serial
Device
Figure 1-6. Backhaul Network
05-4446A01, Rev. A Mercury Reference Manual 9
1.3.5 Multiple Protocols and/or Services
(Future Functionality)
Prior to the introduction of Ethernet/IP-based radios, two radios were often used to service two different types of devices (typically connected to different SCADA hosts). A Mercury radio provides this functionality using a single remote unit. The unit’s serial port can be connected via IP to different SCADA hosts, transporting different (or the same) proto­cols. Both data streams are completely independent and the transceiver provides seamless simultaneous operation as shown in Figure 1-7.
Invisible place holder
RTU
EIA-232
Flow Meter
EIA-232
EIA-232
EIA-232
EIA-232
EIA-232
Serial
Device
Serial
Device
Serial
Device
Serial
Device
NETview
HUB
HUB
WAN
ROUTER
HUB
HUB
SCADA Host Modbus/IP
SCADA Host
Total Flow
Remote Serial
Remote Serial
Access Point
Remote Serial
Access Point
Figure 1-7. Multiple Protocol Network
By using a single radio, the cost of deployment is cut in half. Beyond requiring only one radio instead of two, the biggest cost reduction comes from using half of the required infrastructure at the remote site: one antenna, one feedline, one lightning protector and ancillary hardware. Other cost reductions come from the system as a whole, such as reduced management requirements. And above all, the potential for future appli­cations that run over Ethernet and IP, such as video for remote surveil­lance.
1.3.6 Wireless LAN with Mixed Services
The transceiver is an excellent solution for a long-range industrial wire­less LAN. It offers several advantages over commercial solutions—pri­marily improved performance over extended distances. The rugged construction of the radio and its extended temperature range make it an ideal solution even in harsh locations. In extreme environments, a simple NEMA enclosure is sufficient to house the unit.
10 Mercury Reference Manual 05-4446A01, Rev. A
The transceiver trades higher speed for longer range. Commercial
802.11a/b/g solutions are designed to provide service to relatively small
areas such as offices, warehouses and homes. They provide high data rates but have limited range. The Mercury transmits at a higher power level, uses a different frequency band, has higher sensitivity, and a nar­rower channel to concentrate the radio energy and reach farther dis­tances. It is designed for industrial operation from the ground up.
IP-based devices that may be used with the transceiver include a new breed of more powerful Remote Terminal Units (RTUs) and Program­mable Logic Controllers (PLCs). These, as well as other devices, may be used in applications ranging from SCADA/telemetry monitoring, web-based video, security monitoring, and voice over IP. Figure 1-8 shows a typical wireless IP network.
Invisible place holder
Remote Bridge
IP Camera
IP/Ethernet
IP/Ethernet
IP/Ethernet
NMS Control
Point
SCADA Host
Modbus/IP
Printer
Access Point
Remote Bridge
Figure 1-8. Extended-Range LAN with Mixed Applications
1.3.7 Upgrading Older Wireless Network with Serial Interfaces
Millions of wireless data products have been installed in the last two decades for licensed and license-free operation, many of them manufac­tured by GE MDS. There are several ways that these systems can benefit from incorporating Mercury face flexibility (serial and Ethernet in one unit), and higher data throughput. By taking advantage of its built-in serial and Ethernet inter­faces, the transceiver is well suited to replace leased lines, dial-up lines, or existing 900 MHz “multiple address” data transceivers.
(Future Functionality)
equipment. The chief advantages are inter-
Replacing Legacy Wireless Products
In most cases, legacy radio transceivers supporting serial-interface equipment can be replaced with Mercury transceivers. Legacy equip­ment can be connected to the transceiver through the DB-25 to DB-9 cable wired for EIA-232 signaling. The
COM1
COM1
port with a
port sup­ports all standard EIA-232 signaling and acts as a data-terminal equip­ment device (DTE).
05-4446A01, Rev. A Mercury Reference Manual 11
NOTE: Several previous GE MDS-brand products had non-standard
signal lines on their interface connectors (for example, to control sleep functions and alarm lines). These special func­tions are not provided nor supported by the transceiver. Consult equipment manuals for complete pinout information.
1.4 NETWORK DESIGN
CONSIDERATIONS
1.4.1 Extending Network Coverage with Repeaters
What is a Repeater System?
A repeater works by re-transmitting data from outlying remote sites to the Access Point and vice-versa. It introduces some additional end-to-end transmission delay but provides longer-range connectivity.
In some geographical areas, obstacles can make communications diffi­cult. These obstacles are commonly large buildings, hills, or dense foliage. These obstacles can often be overcome with a repeater station.
Option 1—Using two transceivers to form a repeater station (back-to-back repeater)
Overview
Although the range between fixed transceivers can be up to 40 km (25 miles) over favorable terrain, it is possible to extend the range consider­ably by connecting two units together at one site in a “back-to-back” fashion to form a repeater, as shown in Figure 1-9. This arrangement should be used whenever the objective is to utilize the maximum range between stations. In this case, using high-gain Yagi antennas at each location will provide more reliable communications than their counter­parts—omnidirectional antennas.
Invisible place holder
REPEATER
Access Point
POINT-TO-POINT LINK
Access Point
LAN/WAN
Remote
Ethernet
Crossover Cable
Remote
Figure 1-9. Typical LAN with a Repeater Link
LAN
Remote
LAN
Remote
LAN
Two transceivers may be connected “back-to-back” through the LAN Ports to form a repeater station. (The cable must be a “cross-over” Ethernet cable for this to work). This configuration is sometimes required in a network that includes a distant Remote that would other-
12 Mercury Reference Manual 05-4446A01, Rev. A
wise be unable to communicate directly with the Access Point station due to distance or terrain.
The geographic location of a repeater station is especially important. A site must be chosen that allows good communication with both the Access Point and the outlying Remote site. This is often on top of a hill, building, or other elevated terrain from which both sites can be “seen” by the repeater station antennas. A detailed discussion on the effects of terrain is given in Section 5.1.2, Site Selection (beginning on Page 110).
The following paragraphs contain specific requirements for repeater systems.
Antennas Two antennas are required at this type of repeater station—one for each
radio. Measures must be taken to minimize the chance of interference between these antennas. One effective technique for limiting interfer­ence is to employ vertical separation. In this arrangement, assuming both are vertically polarized, one antenna is mounted directly over the other, separated by at least 10 feet (3 Meters). This takes advantage of the minimal radiation exhibited by most antennas directly above and below their driven elements.
Another interference reduction technique is to cross-polarize the repeater antennas. If one antenna is mounted for polarization in the ver­tical plane, and the other in the horizontal plane, an additional 20 dB of attenuation can be achieved. (Remember that the corresponding stations should use the same antenna orientation when cross-polarization is used.)
Network Name The two radios that are wired together at the repeater site must have dif-
ferent network names. To set or view the network names, see “STEP 3—
CONNECT PC TO THE TRANSCEIVER” on Page 23 for details.
Option 2—Using the AP as a Store-and-Forward Packet Repeater
A wireless network can be extended through the use of an alternate arrangement using the Access Point as a repeater to re-transmit the sig­nals of all stations in the network. The repeater is a standard transceiver configured as an Access Point, and operating in Store and Forward mode. (See Figure 1-10.)
05-4446A01, Rev. A Mercury Reference Manual 13
Invisible place holder
Remote
LAN/WAN
Remote
Access Point
REPEATER
Remote
Remote
LAN
LAN
LAN
Figure 1-10. Typical Store-and-Forward Repeater Arrangement
As with the conventional repeater described in Option 1 above, the loca­tion of a store and forward repeater is also important. A site must be chosen that allows good communication with both the Access Point and the outlying Remote site. This can be on the top of a hill, building, or other elevated terrain from which all sites can be “seen” by the repeater station antenna. A detailed discussion on the effects of terrain is given in Section 5.1.2, Site Selection (beginning on Page 110)
1.4.2 Protected Network Operation using Multiple
Access Points
Although GE MDS transceivers have a very robust design and have undergone intensive testing before being shipped, it is possible for iso­lated failures to occur. In mission-critical applications, down time can be virtually eliminated by using some, or all, of the following configu­rations:
In a point-to-multipoint scenario, the Access Point services multiple remotes. A problem in the Access Point will have an effect on all remotes, since none will have access to the network. When operation of the network does not tolerate any down time, it is possible to set up a protected configuration for the Access Point to greatly reduce the possi­bility of this occurrence.
Two or more Access Points can be configured with the same Network Name and kept active simultaneously, each with its own independent antenna. In this scenario, Remotes will associate with either one of the available Access Points. In case of a failure of one of the AP’s the Remotes will quickly associate with another of the remaining Access Points re-establishing connectivity to the end devices.
The Access Points are unaware of the existence of the other AP’s. Because the hopping algorithm uses both the Network Name and the Wireless MAC address of the AP to generate the hopping pattern, mul­tiple AP’s can coexist—even if they use the same network name. The collocated AP’s will be using different hopping patterns and frequencies the great majority of the time. Although some data collisions will occur, the wireless-MAC is built to tolerate and recover from such occurrences with minimal degradation.
14 Mercury Reference Manual 05-4446A01, Rev. A
1.4.3 Collocating Multiple Radio Networks
Many networks can operate in relatively close physical proximity to one another provided reasonable measures are taken to assure the radio signal of one Access Point is not directed at the antenna of the second Access Point.
The Network Name and the association process
The Network Name is the foundation for building individual radio net­works. It is part of a beacon signal broadcast by the Access Point (AP) to any Remote units with the same Network Name. Remotes that join the network are referred to as being “associated” with the Access Point unit.
Multiple APs with the same Network Name should be used with care. Using the same Network Name in multiple APs may result in Remotes associating with undesired APs and preventing data exchange from occurring as planned.
The use of a different Network Name does not guarantee an interfer­ence-free system. It does however, assure that only data destined for a unique network is passed through to that network.
Co-Location for Multiple Networks
It may be desirable to co-locate Access Points at one location to take advantage of an excellent or premium location that can serve two inde­pendent networks. Each network should have unique Network Name and each AP unit’s antenna should be provided as much vertical separa­tion as is practical to minimize RFI.
NOTE: All transceivers are shipped with the Network Name set to
“Not Programmed.” The Network Name must be programmed in order to pass data and begin normal operations.
Can radio frequency interference (RFI) disrupt my wireless network?
When multiple radio networks operate in close physical proximity to other wireless networks, individual units may not operate reliably under weak signal conditions and may be influenced by strong radio signals in adjacent bands. This radio frequency interference cannot be predicted with certainty, and can only be determined by experimentation. If you need to co-locate two units, start by using the largest possible vertical antenna separation between the two AP antennas on the same support structure. If that does not work, consult with your factory representative about other techniques for controlling radio frequency interference between the radios. (See “A Word About Radio Interference” on
Page 115 for more details.)
05-4446A01, Rev. A Mercury Reference Manual 15
1.5 GE MDS CYBER SECURITY SUITE
Today, the operation and management of an enterprise is becoming increasing dependent on electronic information flow. An accompanying concern becomes the cyber security of the communication infrastructure and the security of the data itself.
The transceiver is capable of dealing with many common security issues. Table 1-2 profiles security risks and how the transceiver pro­vides a solution for minimizing vulnerability.
Table 1-2. Security Risk Management
Security Vulnerability GE MDS Cyber Security Solution
Unauthorized access to the backbone network through a foreign remote radio
“Rogue” AP, where a foreign AP takes control of some or all remote radios and thus remote devices
Dictionary attacks, where a hacker runs a program that sequentially tries to break a password.
Denial of service, where Remote radios could be reconfigured with bad parameters bringing the network down.
Airsnort and other war-driving hackers in parking lots, etc.
802.1x RADIUS authentication
Approved Remotes List (local)
Only those remotes included in the AP list will associate
802.1x RADIUS authentication
Approved AP List
A remote will only associate to those AP included in its local authorized list of AP
Failed-login lockdown
After 3 tries, the transceiver ignores login requests for 5 minutes. Critical event reports (traps) are generated as well.
Remote login with SSH or HTTPS
Local console login
Disabled HTTP & Telnet to allow
only local management services
900 MHz operation is not
interoperable with standard 802.11b wireless cards
The transceiver cannot be put in a
promiscuous mode
Proprietary data framing
Eavesdropping, intercepting messages
Key cracking software
Replaying messages
16 Mercury Reference Manual 05-4446A01, Rev. A
AES-128 encryption
Automatic Rotating Key algorithm
Automatic Rotating Key algorithm
Table 1-2. Security Risk Management
Security Vulnerability GE MDS Cyber Security Solution
Unprotected access to configuration via SNMPv1
Intrusion detection
Implement SNMPv3 secure
operation
Provides early warning via SNMP
through critical event reports (unauthorized, logging attempts, etc.)
Unauthorized AP MAC address
detected at Remote
Unauthorized Remote MAC
address detected at AP
Login attempt limit exceeded
(Accessed via: Telnet, HTTP, or local)
Successful login/logout
(Accessed via: Telnet, HTTP, or local)
1.6 ACCESSORIES
The transceiver can be used with one or more of the accessories listed in
Table 1-3. Contact the factory for ordering details.
Table 1-3. Accessories
Accessory Description GE MDS
AC Power Adapter Kit
Omni­Directional Antennas
Yagi Antenna (Directional)
GPS Receiving Antennas
TNC Male-to-N Female Adapter
TNC Male-to-N Female Adapter Cable
Ethernet RJ-45 Crossover Cable (CAT5)
A small power supply module designed for continuous service. UL approved. Input: 120/220; Output: 13.8 Vdc @ 2.5 A
Rugged antennas well suited for use at Access Point installations. Consult with your factory Sales Representative for details
Rugged antennas well suited for use at fixed Remote sites. Consult with your factory Sales Representative for details.
A variety of fixed and mobile GPS antennas (active and passive) are available. Consult with your factory Sales Representative for details.
One-piece RF adaptor plug. 97-1677A161
Short length of coaxial cable used to connect the radio’s TNC antenna connector to a Type N commonly used on large diameter coaxial cables.
Cable assembly used to cross-connect the Ethernet ports of two transceivers used in a repeater configuration. (Cable length 3 ft./1M)
Part No.
01-3682A02
--
--
--
97-1677A159 (3 ft./1m)
97-1677A160 (6 ft./1.8m)
97-1870A21
05-4446A01, Rev. A Mercury Reference Manual 17
Table 1-3. Accessories (Continued)
Accessory Description GE MDS
2-Pin Power Plug
Ethernet RJ-45 Straight-thru Cable (CAT5)
EIA-232 Shielded Data Cable
EIA-232 Shielded Data Cable
Fuse Small, board-mounted fuse used to protect
Flat-Surface Mounting Brackets & Screws
DIN Rail Mounting Bracket
COM1 Interface Adapter
Bandpass Filter Antenna system filter that helps eliminate
Ethernet Surge Suppressor
Mates with power connector on transceiver. Screw terminals provided for wires, threaded locking screws to prevent accidental disconnect.
Cable assembly used to connect an Ethernet device to the transceiver. Both ends of the cable are wired identically. (Cable length 3 ft./1M)
Shielded cable terminated with a DB-25 male connector on one end, and a DB-9 female on the other end. Two lengths available (see part numbers at right).
Shielded cable terminated with a DB-9 male connector on one end, and a DB-9 female on the other end, 6 ft./1.8m long.
against over-current conditions.
Brackets: 2˝ x 3˝ plates designed to be screwed onto the bottom of the unit for surface-mounting the radio.
Screws: 6-32/1/4˝ with locking adhesive. (Industry Standard MS 51957-26)
Bracket used to mount the transceiver to standard 35 mm DIN rails commonly found in equipment cabinets and panels.
DB-25(F) to DB-9(M) shielded cable assembly (6 ft./1.8 m) for connection of equipment or other EIA-232 serial devices previously connected to “legacy” units. (Consult factory for other lengths and variations.)
interference from nearby paging transmitters.
Surge suppressor for protection of Ethernet port against lightning.
Part No.
73-1194A39
97-1870A20
97-3035L06 (6 ft./1.8m)
97-3035L15 (15 ft./4.6m)
97-1971A03
29-1784A03
82-1753-A01
70-2620-A01
03-4022A02
97-3035A06
20-2822A02
29-4018A01
18 Mercury Reference Manual 05-4446A01, Rev. A
T ABLET OP EV ALU A TION
2
2 Chapter Counter Reset Paragraph
Contents
2.1 OVERVIEW ............................................................................. 21
2.2 STEP 1CONNECT THE ANTENNA PORTS........................ 21
2.3 STEP 2MEASURE & CONNECT THE PRIMARY POWER. 22
2.4 STEP 3CONNECT PC TO THE TRANSCEIVER................. 23
2.5 STEP 4REVIEW TRANSCEIVER CONFIGURATION ......... 23
2.6 STEP 5CONNECT LAN AND/OR SERIAL EQUIPMENT .... 24
AND TEST SETUP
2.5.1 Getting Started ......................................................................... 23
2.5.2 Procedure ................................................................................. 23
2.5.3 Basic Configuration Defaults .................................................... 23
2.7 STEP 6CHECK FOR NORMAL OPERATION ..................... 25
05-4446A01, Rev. A Mercury Reference Manual 19
20 Mercury Reference Manual 05-4446A01, Rev. A
2.1 OVERVIEW
It is recommended that a “tabletop network” be set up to verify the basic operation of the transceivers. This allows experimenting with network designs, configurations or network equipment in a convenient location. This test can be performed with any number of radios.
When you are satisfied that the network is functioning properly in a benchtop setting, field installation can be performed. Complete informa­tion for field installation, including mounting dimensions and antenna selection, is provided in INSTALLATION PLANNING on Page 109.
NOTE: It is important to use a “Network Name” that is different from
any currently in use in your area during the testing period.
To simulate data traffic over the radio network, connect a PC or LAN to the Ethernet port of the Access Point and PING each transceiver several times.
2.2 STEP 1—CONNECT THE ANTENNA
PORTS
Figure 2-1 is a drawing of the tabletop arrangement. Connect the
antenna ports of each transceiver as shown. This provides stable radio communications between each unit and prevents interference to nearby electronic equipment.
Invisible place holder
Remote
POWER ATTENUATORS
• Fixed or adjustable
• 1W Minimum Rating
Access Point
NON-RADIATING ATTENUATORS
COMPUTER
POWER DIVIDER
• Install on unused divider ports (if any)
• 1W Minimum Rating
Figure 2-1. Typical setup for tabletop-testing of radios
Remote
Remote
05-4446A01, Rev. A Mercury Reference Manual 21
NOTE: It is important to use attenuation between all units in the test
setup. The amount of attenuation required will depend on the number of units being tested and the desired signal strength (RSSI) at each transceiver during the test. In no case should a signal greater than –50 dBm be applied to any transceiver in the test setup. An RF power output level of +20 dBm is recom­mended from the AP. Remote power is not settable. (See “Radio Conguration Menu” on Page 52.)
2.3 STEP 2—MEASURE & CONNECT
THE PRIMARY POWER
The primary power at the transceiver’s power connector must be within
10.5–30 Vdc and be capable of continuously providing 30 Watts. Typ­ical power consumption for 13.8 and 24 Vdc operation are listed in
SPECIFICATIONS on Page 123.
A Phoenix two-pole power connector with screw-terminals is provided with each unit. Strip the wire leads to 6 mm (0.25"). Be sure to observe proper polarity with the positive lead (+) on the left and negative (–) on the right.
NOTE: It typically requires about 30 seconds for the transceiver to power
up, and may take several minutes to associate with another unit, if GPS is required for time synchronization.
GPS is required for all configurations except when “Free Run” single-channel (non-frequency hopping) operation is used, which may be possible in some low-interference environments.
CAUTION
POSSIBLE
EQUIPMENT
DAMAGE
The transceiver must only be used with nega­tive-ground power systems. Make sure the polarity of the power source is correct.
Invisible place holder
Figure 2-2. Power Connector
(Polarity: Left +, Right –)
22 Mercury Reference Manual 05-4446A01, Rev. A
2.4 STEP 3—CONNECT PC TO THE
TRANSCEIVER
Connect a PC’s Ethernet port to the LAN port using an Ethernet cross­over cable. The serial cable to connect to the
LAN LED should light. Alternatively, you can use a
COM1 port. (Figure 2-3 on Page 24)
2.5 STEP 4—REVIEW TRANSCEIVER
CONFIGURATION
2.5.1 Getting Started
Start by logging into the Access Point radio. This is done first because the Remotes are dependent on the AP’s beacon signal to achieve an “associated” state.
Once the Access Point is up and running, move the computer connection to each of the Remote units, log-in at each unit, review their configura­tion, set their IP addresses and Network Name and wait for each to achieve an associated state.
With all units associated, you will be ready to connect and test your data services.
2.5.2 Procedure
The following is a summary of the configuration procedure that must be done on each unit in the system. Key parameters are shown on the Embedded Management System overview (Figure 3-1 on Page 29). A lists of parameters can found in two tables—Table 4-5 on Page 98 and
Table 4-7 on Page 101. Detailed information on using the Management
System can be found in MS INTRODUCTION on Page 28.
NOTE: The Management System supports the use of “configuration
files” to aid in uniformly configuring multiple units. These are explained in Conguration Scripts Menu on Page 79.
2.5.3 Basic Configuration Defaults
Table 2-1 provides a selection of key operating parameters, their range,
and default values. All of these are accessible through a terminal emu­lator connected to the nected to the
NOTE: Access to the transceiver’s Management System and changes
LAN Port. (See Figure 5-1 on Page 109 for hookup.)
to some parameters, require the entry of a password to main­tain security.
COM1 serial port or through a Web browser con-
05-4446A01, Rev. A Mercury Reference Manual 23
Table 2-1. Basic Configuration Defaults
Item Menu Location Default Values/Range
Network Name Main Menu>>
IP Address Main Menu>>
RF Output Power
(adjustable only at AP)
Unit Password Main Menu>>
Network Configuration>> Network Name
Network Configuration>> IP Address
Main Menu>> Radio Configuration>> RF Output Power
Device Information>> User Password
“Not Programmed”
192.168.1.1 Contact your network
30 dBm (1.0 Watt)
admin (lower case)
• 1–15 alphanumeric characters
• Case-sensitive; can be mixed case
administrator
20–30 dBm @ 50Ω (0.1–1.0 Watts)
• 1–8 alphanumeric characters
• Case-sensitive; can be mixed case
A unique IP address and subnet are required to access the browser-based Management System either through the
LAN port, or remotely
over-the-air.
2.6 STEP 5—CONNECT LAN AND/OR SERIAL EQUIPMENT
Connect a local area network to the LAN port or a serial device to the
COM1 (DCE) port. The LAN port will support any Ethernet-compatible
equipment. This includes devices that use Internet Protocol (IP).
Figure 2-3 shows the interface connectors on the front panel of the trans-
ceiver.
Invisible place holder
PANEL
RX2 ANTENNA
GPS ANTENNA
CONNECTION
PORT
ANTENNA PORT
TX/RX1
LAN PORT
DC POWER INPUT
(10—30 VDC, 2.5A)
LED INDICATOR
COM1
SERIAL PORT
Figure 2-3. Transceiver Interface Connectors
24 Mercury Reference Manual 05-4446A01, Rev. A
LED INDICATOR PANEL—Displays the basic operating status of the transceiver. Section 2.7 contains detailed information.
COM1 SERIAL PORT— DB-9 connector used for management
of the transceiver via a connected PC. MS INTRODUCTION on
Page 28 provides complete connection details.
LAN PORT—Connection point for Ethernet Local Area Net-
work. An integrated LED on this port glows yellow for 10 mbps, green for 100 mbps.
PWR— DC power connection for the transceiver. Power source
must be 10–30 Vdc, negative ground, and capable of furnishing at least 10 watts.
GPS ANTENNA PORT— Coaxial connector (SMA-type) for
connection of a Global Positioning System receiving antenna. Provides 3.5 Vdc output for compatibility with powered (active) GPS antennas.
NOTE: GPS functionality is required on all Access Points and
Remotes except when “Free Run” single-channel (non-frequency
hopping) operation is used, which may be possible in some low-interference environments.
RX2 ANTENNA PORT— Coaxial connector (TNC-type) for attachment of a second 900 MHz receiving antenna used in space diversity arrangements.
TX/RX1 ANTENNA PORT— Coaxial connector (TNC-type) for
attachment of the main station antenna (transmit and receive).
2.7 STEP 6—CHECK FOR NORMAL OPERATION
Once the data equipment is connected, you are ready to check the trans­ceiver for normal operation.
Observe the LEDs on the top cover for the proper indications. In a nor­mally operating system, the following LED indications will be seen within 45seconds of start-up:
PWR—Lit continuously
LINK—On, or blinking intermittently to indicate traffic flow
LAN—On, or blinking intermittently to indicate traffic flow
Figure 2-4 shows a close-up view of the transceiver’s LED Indicator
panel. Table 2-2 provides details on each LED function.
05-4446A01, Rev. A Mercury Reference Manual 25
Invisible place holder
Figure 2-4. LED Indicator Panel
If the radio network seems to be operating properly based on observa­tion of the unit’s LEDs, you can use the
PING command to verify the link
integrity with the Access Point. This command can also be used to point your browser to another Remote unit’s IP address in the same network.
Table 2-2. Transceiver LED Functions
LED Label Activity Indication
PWR ON Primary power (DC) present
Blinking Unit in “Alarmed” state
OFF Primary power (DC) absent
LAN* ON LAN detected
Blinking Data TX/RX
OFF LAN not detected, or excessive
COM1 (MGT System)
GPS ON Internal GPS receiver is
LINK
(Access Point)
LINK
(Remote)
Blinking Data TX/RX
OFF No data activity
OFF Internal GPS receiver is not
ON Default state
Blinking Data Tx/Rx
OFF Traffic exceeds the capacity of
ON Associated to AP
Blinking Data Tx/Rx
OFF Not associated with AP
traffic present
synchronized with the satellite network.
synchronized with the satellite network.
the radio network
* The
LAN connector itself has an integrated LED which glows yellow
for 10 mbps operation, and green for 100 mbps.
26 Mercury Reference Manual 05-4446A01, Rev. A
EMBEDDED
3
3 Chapter Counter Reset Paragraph
Contents
3.1 MS INTRODUCTION............................................................... 28
3.2 ACCESSING THE MENU SYSTEM ........................................ 30
3.3 BASIC DEVICE INFORMATION.............................................. 36
3.4 CONFIGURING NETWORK PARAMETERS .......................... 41
MANAGEMENT SYSTEM
3.1.1 Differences in the User Interfaces ............................................ 28
3.2.1 Methods of Control ................................................................... 31
3.2.2 PC Connection & Log In Procedures ....................................... 31
3.2.3 Navigating the Menus .............................................................. 35
3.3.1 Starting Information Screen ..................................................... 36
3.3.2 Main Menu ............................................................................... 38
3.3.3 Configuring Basic Device Parameters ..................................... 39
3.4.1 Network Configuration Menu ................................................... 41
3.4.2 IP Configuration Menu ............................................................. 42
3.4.3 Ethernet Port Configuration Menu ........................................... 43
3.4.4 Bridge Configuration ................................................................ 44
3.4.5 VLAN Configuration ................................................................. 45
3.4.6 SNMP Agent Configuration ...................................................... 46
3.4.7 Wireless Network Configuration (AP Only) ............................... 49
3.4.8 AP Location Info Config Menu (Remote Only) ......................... 49
3.4.9 DHCP Server Configuration (AP Only) .................................... 50
3.4.10 SNTP Server Configuration .................................................... 51
3.5 RADIO CONFIGURATION ...................................................... 51
3.5.1 Radio Configuration Menu ..................................................... 52
3.5.2 Frequency Control Menu ......................................................... 53
3.5.3 Advanced Configuration Menu ................................................. 54
3.5.4 Security Configuration .............................................................. 55
3.5.5 Redundancy Configuration (AP Only) ...................................... 61
3.5.6 GPS Configuration (Remote Only) ........................................... 66
3.5.7 Performance Information Menu ............................................... 66
3.5.8 Maintenance/Tools Menu ......................................................... 74
3.6 PERFORMANCE OPTIMIZATION .......................................... 85
3.6.1 Proper OperationWhat to Look For 88
05-4446A01, Rev. A Mercury Reference Manual 27
3.1 MS INTRODUCTION
The transceiver’s embedded management system is accessible through various data interfaces. These include the
(Ethernet) port, and via SNMP. Essentially the same capabilities are
available through any of these paths.
For support of SNMP software, a set of MIB files is available for down­load from the GE MDS Web site at www.GEmds.com. An overview of SNMP commands can be found at SNMP Agent Conguration section
on Page 46 of this manual.
The transceiver’s Management System and its functions are divided into seven functional groups as listed below.
Section 3.3, BASIC DEVICE INFORMATION (beginning on
Page 36)
Section 3.4, CONFIGURING NETWORK PARAMETERS
(beginning on Page 41)
Section 3.5, RADIO CONFIGURATION (beginning on Page
51)
Section 3.5.4, Security Conguration (beginning on Page 55)
Section 3.6, PERFORMANCE OPTIMIZATION (beginning on
Page 85)
Section 3.5.8, Maintenance/Tools Menu (beginning on Page 74)
COM1 (serial) port, LAN
Each of these sections has a focus that is reflected in its heading. The section you are now reading provides information on connecting to the Management System, how to navigate through it, how it is structured, and how to perform top-level configuration tasks. Figure 3-1 on the fol­lowing page shows a top-level view of the Management System (MS).
3.1.1 Differences in the User Interfaces
Although there are slight differences in navigation among the user inter­faces, the content is very similar. You will notice a few differences in capabilities as the communications tool is driven by limitations of the access channel. Figure 3-2 and Figure 3-3 show examples of the Starting Information Screen as seen through a console terminal and a web-browser, respectively.
28 Mercury Reference Manual 05-4446A01, Rev. A
Maintenance/Tools
Information
Performance
Device
Information
MAIN MENU
(Read-Only Status)
Redundancy
Configuration (AP)
Starting Information Screen
Reprogramming
Config. Scripts
Ping Utility
Auth. Codes
Wireless Ntwk Stat.
GPS Status
Packet Statistics
Event Log
Date
Model
Redundancy Config.
Uptime
Serial Number
Ntwk Event Triggers
Radio Event Triggers
Hdwr Event Triggers
Reset to Defaults
Radio Test
Intl. Radio Stat. (RM)
Time
Date Format
Console Bd. Rt.
Device Names
UTC Time Offset
GPS
Red. Config. Options
Force Switchover
Configuration (RM)
Stream GPS
Send GPS via UDP
GPS IP Address
GPS Server Port
Security
Configuration
RADIUS
Device Security
Configuration
Wireless Security
Manage Certif.
Radio
Network Name
Transmit Pwr (AP)
Freq. Control
Receive Pwr (AP)
Freq. Control
Configuration
Adv. Config.
Network
IP Configuration
Ethernet Port Config
Bridge Configuration
VLAN Configuration
SNMP Agent Config. (AP)
SMTP Agent Config. (RM)
Wireless Ntwk Config. (AP)
AP Location Info (RM)
DHCP Server Config.
Configuration
SNTP Server Config.
• Spacebar is used to make some menu selections
NOTES
• Char t shows top-level view only. See Reference Manual for details.
• Not all menu items are-user configurable
• AP = Access Point Only
• RM = Remote Only
Figure 3-1. Embedded Management System—Top-Level Flowchart
05-4446A01, Rev. A Mercury Reference Manual 29
Figure 3-2. View of MS with a text-based program—
(Console Terminal shown—Telnet has similar appearance)
Invisible place holder
Figure 3-3. View of the MS with a Browser
(Selections at left provide links to the various menus)
3.2 ACCESSING THE MENU SYSTEM
The radio has no external controls or adjustments. All configuration, diagnostics and control is performed electronically using a connected PC. This section explains how to connect a PC, log into the unit, and gain access to the built-in menus.
30 Mercury Reference Manual 05-4446A01, Rev. A
Loading...
+ 108 hidden pages