GE MDS iNET Series, Setup Manual

Page: 1 / 4

05-2873A01, Rev. F MDS iNET Series Setup Guide 1
MDS iNET Series
Setup Guide
This guide provides installation instructions for MDS iNET Series
transceivers (
Figure 1). It covers both MDS iNET-II and iNET
models. For detailed product information, refer to the
Technical Manual, part no. 05-2806A01. It contains important
notices on the safe and effective use of this product and
should be reviewed prior to any operation.
Electronic copies of all GE MDS manuals are available free of
charge at www.gemds.com.
Invisible place holder
Figure 1. MDS iNET Series Transceiver
MDS iNET transceivers provide wireless connectivity for local area
networks (LANs) with easily installed hardware. The units come in
two primary models—
Access Point (AP) and Remote .
An AP is a wireless “hub” that normally provides connectivity into a
wired Ethernet LAN/WAN. It serves as the network’s “master
station” providing synchronization data to all associated Remotes
within the network.
Three types of Remotes are available—the Ethernet Bridge, the
Serial Gateway, and the Dual Gateway which supports both
IP/Ethernet and serial services.
Table 1 summarizes the different
interface abilities for each AP and Remote radio type.
A given transceiver may be configured to operate as an Access
Point or a Remote with certain restrictions. The following rules
apply to unit configuration:
1. A Serial or Ethernet Remote can be changed from one to the
other without an Authorization code.
2. If both the Serial and Ethernet Authorization Codes are entered,
the Remote becomes a Dual Gateway. Each code is associated
with the serial number of a particular radio.
3. A Dual Gateway Remote can be reconfigured as an Access
Point. by entering an Access Point Authorization Code from the
Factory.
4. An Access Point can be reconfigured as a Dual Gateway by
changing the device mode in the management interfaces.
2.0.1 Differences Between iNET-II and iNET
The iNET-II and iNET Transceivers, while similar in many
respects, do have important differences and are
not over-the-air
compatible. Key differences are summarized in Table 2 :
Table 2. Transceiver Differences (iNET vs. iNET-II)
2.1 SECURITY FEATURES
The transceiver is capable of dealing with many common security
issues.
Table 3 profiles security risks and how the transceiver
provides a solution for minimizing vulnerability. In all cases, the
Security Configuration Menu should be reviewed and set to the
required parameters for your environment. Consult with your
network administrator if you are unsure of the required settings.
3.0.1 General Requirements
There are three main requirements for installing the transceiver:
1. Adequate and stable primary power
2. A good antenna system
3. The correct interface between the transceiver and connected
equipment
Figure 2 shows a typical installation for a Remote site. AP sites are
similar, but typically use an omnidirectional antenna to allow for
communication with widely distributed Remote stations.
1.0 INTRODUCTION
2.0 PRODUCT DESCRIPTION
Table 1. Transceiver Models and Interfaces
Model Type LAN
1
COM1
1
COM2
Access Point
2 N/A Yes Yes Yes
Remote…
Ethernet Bridge
3, 4 Yes No No
Serial Gateway
3, 4
No Yes Yes
Dual Gateway
3
Yes Yes Yes
NOTES
1. Provides PC access to the Menu System on all units.
2. Can be configured as an Access Point or Dual Gateway.
3. An Ethernet Bridge can be configured as a Serial Gateway and
vice versa.
4. Can be upgraded to Dual Gateway with an Authorization Key.
Characteristic iNET-II iNET
Data Rate 512 kbps/1 Mbps 256/512 kbps
FCC Certification Type DTS FHSS
Encryption AES-128 RC4-128
Channel size 600 kHz 316.5 kHz
Channel operation Channels Zones
Firmware Specific for iNET-II Specific for iNET
Table 3. Cyber Security Highlights
Security Level Specification
• MDS Cyber Security
Suite, Level 4: • AES-128 encryption (iNET-II only)
• 802.1Q VLAN
• Includes Level 3 features listed below
• MDS Cyber Security
Suite, Level 3: • RC4-128 encryption (iNET only)
• Automatic rotating key algorithm
• Authentication: 802.1x, RADIUS, EAP/TLS,
(PKI is a requirement of the TLS), PAP,
CHAP.
• Local Device authentication using MAC
address “white lists” on the AP and Remote
• Management: SSL, SSH, HTTPS
• Failed login lockdown
• 900 MHz operation and proprietary data
framing
3.0 INSTALLATION