MDS Orbit MCR-4G Technical Manual

MDSTM Orbit MCR-4G
Managed Connected Router 4G and WiFi
Technical Manual
MDS 05-6628A01, Rev. C
NOVEMBER 2013
Installation and Operation Guide
Visit our website for downloadable copies of all documentation at www.gemds.com.
TABLE OF CONTENTS
1.0 INTRODUCTION .................................................................................................................. 1
1.1 About This Manual ........................................................................................................................ 1
Software Command Notations ......................................................................................................... 1
2.0 PRODUCT DESCRIPTION................................................................................................... 3
2.1 Key Features .................................................................................................................................3
2.2 Interface Types .............................................................................................................................. 3
2.3 Typical Application ......................................................................................................................... 3
2.4 Connectors and Indicators ............................................................................................................ 4
Grounding Considerations ...............................................................................................................9
Mounting Options...........................................................................................................................10
Optional DIN Rail Mounting ...........................................................................................................10
Antenna Planning & Installation ................................................................................................... 11
Accessories and Spares ................................................................................................................ 13
3.0 Device Management........................................................................................................... 14
3.1 Connecting to a PC ..................................................................................................................... 14
Differences Between Serial & SSH................................................................................................14
Establishing Communication—Serial Interface..............................................................................14
Setting Basic Parameters—First Steps..........................................................................................15
One-Time “Recovery” Passwords.................................................................................................. 16
3.2 Pre-Configured Settings .............................................................................................................. 17
3.3 YANG Interface ............................................................................................................................18
CLI Login Prompt ........................................................................................................................... 19
3.4 Operational Topic Areas ..............................................................................................................25
Serial Console ........................................................................................................................ 26
Network ..................................................................................................................................27
LAN ........................................................................................................................................30
VLAN Operation ..................................................................................................................... 33
Cell .........................................................................................................................................34
WiFi ........................................................................................................................................37
Bridging ..................................................................................................................................42
Routing ...................................................................................................................................45
Firewall and NAT .................................................................................................................... 46
Packet Filtering ......................................................................................................................48
Network Address Translation (NAT) ...................................................................................... 51
VPN ........................................................................................................................................56
DNS ........................................................................................................................................63
DHCP Service ........................................................................................................................ 64
Iperf Service ........................................................................................................................... 66
Date, Time and NTP ..............................................................................................................67
Geographical-location ............................................................................................................ 68
User Management and Access Controls ................................................................................ 69
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual i
Login-Lockout ......................................................................................................................... 71
RADIUS ..................................................................................................................................72
File Servers ............................................................................................................................ 73
Certificate Management .........................................................................................................74
Event Logging ........................................................................................................................81
Firmware Management ..........................................................................................................82
Support Bundle ......................................................................................................................84
Configuration Scripts .............................................................................................................. 85
4.0 Technical Reference ........................................................................................................... 86
4.1 Troubleshooting ........................................................................................................................... 86
LED Status Indicators ....................................................................................................................86
4.2 Technical Specifications .............................................................................................................. 87
General .......................................................................................................................................... 87
Physical.......................................................................................................................................... 87
Environmental ................................................................................................................................ 87
Agency/Regulatory Approvals........................................................................................................87
2.4 GHz WiFi Specifications...........................................................................................................87
4.3 Glossary of Terms & Abbreviations ............................................................................................. 88
APPENDIX A – Data Configuration Tree .................................................................................... 90
APPENDIX B – Command Line Interface (CLI) Features......................................................... 104
APPENDIX C – Integrity Measurement Authority (IMA) ........................................................... 120
APPENDIX D – Common Event Expression (CEE).................................................................. 123
APPENDIX E– Configuring Firmware Management ................................................................. 127
APPENDIX F– Obtaining Provisioned Cell Service (Verizon)................................................... 129
APPENDIX G – Device Manager.............................................................................................. 130
11.1 Web Browser Connection ........................................................................................................ 130
APPENDIX H – Licenses .......................................................................................................... 132
Copyright and Trademark
This manual and all software described herein is protected by Copyright: 2013 GE MDS, LLC. All rights reserved. GE MDS, LLC reserves its right to correct any errors and omissions in this publi­cation.
ii MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C
RF Safety Notice (English and French)
RF Exposure
l'exposition aux RF
Concentrated energy from a directional antenna may pose a health hazard to humans. Do not allow people to come closer to the antenna than the distances listed in the table below when the transmitter is operating. More information on RF exposure can be found online at the following website: www.fcc.gov/oet/info/documents/bulletins.
Concentré d'énergie à partir d'une antenne directionnelle peut poser un risque pour la santé humaine. Ne pas permettre aux gens de se rapprocher de l'antenne que les distances indiquées dans le tableau ci-dessous lorsque l'émetteur est en marche. Plus d'informations sur l'exposition aux RF peut être trouvé en ligne à l'adresse suivante: www.fcc.gov / oet / info / documents et bulletins.
Antennas must not be co-located. All transmission antennas must be at least 20 cm apart to comply with FCC co-location rules.
Orbit Device vs. Minimum RF Safety Distance
Radio Module Type
MCR-4G 20 cm
MCR-900 23 cm
Other models Consult factory prior to operation.
Minimum Safety Distance
from Antenna
FCC Part 15 Notice
Operation is subject to the following two conditions: (1) this device may not cause harmful inter­ference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Any unauthorized modification or changes to this device without the express approval of the manufacturer may void the user’s authority to operate this device. Further­more, this device is intended to be used only when installed in accordance with the instructions out­lined in this manual. Failure to comply with these instructions may void the user’s authority to operate this device.
Industry Canada Notice
This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
Operational Safety Notices
The MDS Orbit MCR-4G may not be used in an environment where radio frequency equipment is prohibited or restricted in its use. This typically includes aircrafts, airports, hospitals, and other sen­sitive electronic areas.
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual iii
Do not operate RF devices in an environment that may be susceptible to radio interference resulting in danger, specifically:
Areas where prohibited by law
Follow any special rules and regulations and obey all signs and notices. Do not use the MCR-4G when you suspect that it may cause interference or danger.
Near Medical and life support equipment
Do not use the MCR-4G in any area where medical equipment, or life support equipment may be located, or near any equipment that may be susceptible to any form of radio interference.
Cellular Operational Bands
The following table shows the bands in which the cellular module operates for each wireless tech­nology.
FCC IDs of Installed Transmitters
As of the printing date, the following identifiers are assigned to the modules listed below. For the latest, official listings of all agency approvals, please contact your factory representative.
CELL Modem FCC ID: PKRNVWE362, IC ID: 3229B:E362 WIFI Module FCC ID: M4Y-ZCN722MV1, IC ID 3195A-ZCN722MV1
CE Mark and RTTE Notice
This product, using the "WIFI internal radio module" only, is CE marked and compliant with the RTTE directive. Other configurations will be added for EU use in future releases.
iv MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C
Servicing Precautions
No user-serviceable parts are contained inside this equipment. Opening of the unit by unauthorized personnel voids the warranty. All servicing must be performed by an authorized repair facility.
When servicing energized equipment, be sure to wear appropriate Personal Protective Equipment (PPE). During internal service, situations could arise where objects accidentally contact or short circuit components and the appropriate PPE would alleviate or decrease the severity of potential injury. When servicing equipment, all workplace regulations and other applicable standards for live electrical work should be followed to ensure personal safety.
Manual Revision and Accuracy
This manual was prepared to cover a specific version of firmware code. Accordingly, some screens and features may differ from the actual unit you are working with. While every reasonable effort has been made to ensure the accuracy of this publication, product improvements may also result in minor differences between the manual and the product shipped to you. If you have additional ques­tions or need an exact specification for a product, please contact GE MDS using the information at the back of this guide. In addition, manual updates can be found on our web site at www.gemds.com
Environmental Information
The manufacture of this equipment has required the extraction and use of natural resources. Improper disposal may contaminate the environment and present a health risk due to hazardous substances contained within. To avoid dissemination of these substances into our environment, and to limit the demand on natural resources, we encourage you to use the appropriate recycling sys­tems for disposal. These systems will reuse or recycle most of the materials found in this equipment in a sound way. Please contact GE MDS or your supplier for more information on the proper dis­posal of this equipment.
Battery Disposal—This product may contain a battery. Batteries must be disposed of properly, and
may not be disposed of as unsorted municipal waste in the European Union. See the product doc­umentation for specific battery information. Batteries are marked with a symbol, which may include lettering to indicate cadmium (Cd), lead (Pb), or mercury (Hg). For proper recycling return the battery to your supplier or to a designated collection point. For more information see: www.weeerohsinfo.com.
Product Test Data Sheets
Test Data Sheets showing the original factory test results for this unit are available upon request from the GE MDS Quality Leader. Contact the factory using the information at the back of this manual. Serial numbers must be provided for each product where a Test Data Sheet is required.
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual v
CSA/us Notice
EXPLOSION
HAZARD!
This product is approved for use in Class 1, Division 2, Groups A, B, C & D Hazardous Locations. Such locations are defined in Article 500 of the National Fire Protection Association (NFPA) pub­lication NFPA 70, otherwise known as the National Electrical Code. The transceiver has been rec­ognized for use in these hazardous locations by the Canadian Standards Association (CSA) which also issues the US mark of approval (CSA/US). The CSA Certification is in accordance with CSA STD C22.2 No. 213-M1987.
CSA Conditions of Approval: The transceiver is not acceptable as a stand-alone unit for use in the hazardous locations described above. It must either be mounted within another piece of equipment which is certified for hazardous locations, or installed within guidelines, or conditions of approval, as set forth by the approving agencies. These conditions of approval are as follows: The transceiver must be mounted within a separate enclosure which is suitable for the intended application.The antenna feedline, DC power cable and interface cable must be routed through conduit in accor­dance with the National Electrical Code. Installation, operation and maintenance of the transceiver should be in accordance with the transceiver's installation manual, and the National Electrical Code. Tampering or replacement with non-factory components may adversely affect the safe use of the transceiver in hazardous locations, and may void the approval. A power connector with screw-type retaining screws as supplied by GE MDS must be used.
Do not disconnect equipment unless power has been switched off or the area is known to be non-hazardous. Refer to Articles 500 through 502 of the National Electrical Code (NFPA 70) for further information on hazardous locations and approved Division 2 wiring methods.
vi MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C

1.0 INTRODUCTION

The MCR-4G Setup Guide, Part no. 05-6702A01, contains installation instructions, as well as basic startup information for this product.
All GE MDS user manuals and updates are available online at www.gemds.com.
This manual describes the MDS Orbit MCR-4G Managed Connected Router (Figure 1). The unit is a highly secure, industrial grade, wireless communication product for broad-based applications including control center monitoring, well site pad operations, and video surveillance. It serves the need for localized WiFi communications with a cellular back-up or backhaul option, while providing the extended temperature range and industrial-grade packaging inherent to GE MDS products. These features allow the best use of communication options at each installation site.
Figure 1. MCR-4G Unit
(Standard 2E1S configuration shown)
With a common hardware architecture and user interface, the MCR offers flexibility in network design and application, with simplified training, maintenance, and deployment costs. GE MDS provides an array of communication products with multiple interface options and a variety of enclosures to give customers the choice and flexibility to design their communications network to meet geographic and industry specific challenges. Information on other GE MDS products can be found by visiting our website at www.gemds.com.

1.1 About This Manual

This manual is intended for systems engineers, network administrators, and others responsible for planning, commissioning, using, and troubleshooting the wireless system. Installation steps are not included in this publication. For installation instructions, refer to the companion MCR-4G Setup Guide, part no. 05-6702A01. Electronic copies of all user documentation are available free of charge at www.gemds.com.

1.1.1 Software Command Notations

The product is designed for software control via a connected PC. As such, there are no external controls or adjustments present. To show the names of software commands, keyboard entries, or other information dis­played on a PC screen, a bolded font is used throughout the manual. In the case of tabular data displayed on a PC screen, a variation on this font is used to maintain proper layout. (See examples that follow.)
Bolded font example (used in text for software commands and keyboard entries)
Bolded font example (used to show tables displayed on a PC screen)
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual 1
In the Device Management section of this manual (Section 3.0), there are a number of command strings where information is presented by the unit, and a reply is required from the user. In such cases, information from the unit is shown in a non-bolded font, and the user response is shown in bold. For example:
(none) login: admin
Further, in some cases, command lines will be shown with non-bolded, italicized text contained within the string. Such text indicates the need for user-supplied variable parameters, such as the name of an item. For example:
set interfaces interface myBridge virtual-type bridge
In the above example, you would enter the specific name of your bridge to complete the entry.
NOTE: The software commands and responses shown in this manual were obtained from a unit operating
in a lab environment. The information displayed may differ from field service conditions.
2 MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C

2.0 PRODUCT DESCRIPTION

The MCR-4G is a rugged networking router providing comprehensive solutions for IP/Ethernet, serial, and machine-to-machine wireless communication. This industrial package provides integrated 4G LTE wireless technology and connectivity for Ethernet and serial devices requiring secure operation.

2.1 Key Features

MCR units include the following key features:
Security—The unit uses industry-leading security features to protect data while maintaining com-
patibility with deployed infrastructures. Features include AAA user access with passwords and lock­out protection, VPNs, signed firmware, secure booting, integrity management, and more.
NOTE: The Orbit MCR device is designed for high security environments. As such, management of the
device does not support Telnet, but instead implements the more secure SSH protocol.
Small Form Factor—The unit is housed in a rugged enclosure suited for operation in harsh indus-
trial environments. It requires only protection from direct exposure to the weather, and may be easily mounted inside a NEMA enclosure for outdoor applications when required.
Network Interfaces—Several network interfaces are present to provide connectivity for a variety
of equipment and applications. Ethernet, serial, and WiFi interfaces provide local connections while a cellular interface provides access to public carrier networks.
User Interface—Multiple user interfaces are provided for configuration and monitoring of the unit.
These include local serial console, web, SSH, USB, and NETCONF.
NOTE: When the unit is installed in hazardous locations, use only the serial or Ethernet connections on
the unit’s front panel. Do not use the USB port in hazardous locations.
NETCONF—A next-generation management protocol is used that provides an array of features for
device configuration and monitoring.
Network Management System—The PulseNET Network Management System allows administer-
ing and monitoring the operation of small-to-large scale deployments.

2.2 Interface Types

MCR units are offered in two external interface offerings; 2 Ethernet/1 Serial (2E1S), or 2 Serial/1 Ethernet (2S1E). The 2E1S configuration (Figure 1) is the standard model and is the focus of this manual. Most infor­mation applies equally to both configurations, however.

2.3 Typical Application

The unit provides flexibility in network communications and may be used in a wide variety of applications. In a common scenario, it provides cellular connectivity to locally-connected devices that are located on a local/internal/private LAN or WiFi network. The unit acts as an Access Point on the WiFi interface to pro­vide connectivity to WiFi clients. Figure 2 shows an example network in whic h the unit provides connec­tivity to multiple end devices. The end devices are connected via Ethernet, serial, and WiFi links.
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual 3
Invisible place holder
DC Power (10-60 Vdc)
Ethernet Ports (RJ-45 10/100)
Mini USB
Port
Cellular
Antennas
(Aux & Main)
SIM Card
Slot
COM Port
WiFi Antenna
LED Indicator Panel
Figure 2. Typical MCR Application

2.4 Connectors and Indicators

Figure 3 shows the unit’s front panel connectors and indicators. These items are referenced in the
text that follows. The unit’s LED Indicator Panel is described in Table 4 on Page 9.
Figure 3. Connectors and Indicators
(2E1S configuration shown)
4 MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C
PWR—Two-conductor DC input connection. The unit includes a 6-foot (1. 83 meter) power cable suitable
Lead Screws (2)
Binding
Wire Ports (2)
(Polarity: Left +, Right –)
Retaining Screws (2)
for indoor or outdoor use when properly connected. The DC power connector (Figure 4) is keyed, and can only be inserted one way.
Invisible place holder
Figure 4. DC Power Connector (P/N 73-1194A39)
NOTE: The unit is designed for use in negative ground DC power systems only.
Input voltage to the unit must be well filtered, and within the range of 10-60 Vdc. The maximum rated power consumption of the device is 15 watts, but actual power may be much less, depending on configuration. The power supply must be capable of supplying the expected maximum power for the installation. For expected power requirements in common configurations, see “Technical Specifications” on Page 86.
ETH1 / ETH2— Ethernet connection port. These ports support both device management and payload data transport. Depending on product version, the unit may have one or two Ethernet ports. This is a standard RJ-45 jack, and features MDIX auto-sensing capability, allowing straight-through or crossover cables to be used.
Connecting to the unit via SSH supports device management and provides the same user interface available using the unit’s
COM1 serial port. Various options are available for passing Ethernet data, allowing system
administrators to optimize the configuration for maximum efficiency, based on the system’s operating char­acteristics.
(As viewed from the outside of the unit)
Table 1. ETH1/2 Pin Details
Pin Function
1
Transmit Data (TX) High
2
Transmit Data (TX) Low
3
Receive Data (RX) High
4
Unused
5
Unused
6
Receive Data (RX) Low
7
Unused
8
Unused
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual 5
USB Port—This port allows for connection of a laptop or PC. The port provides a local console for man­agement of the device. A standard host-to-mini device USB 2.0 cable may be used.
COM Port—This
connector serves as the serial interface port for both console management and payload
data. By default, the port is enabled for local console control. The COM port serves as the primary interface for connecting the unit to an external DTE serial device supporting RS-232 or RS-485. If necessary, an adapter may be used to convert the unit’s RJ-45 serial jack to a DB-9F type (GE MDS 73-2434A12).
NOTE: Not all PCs include a serial port. If one is not available, the unit’s USB port may be used to access
the device management interface. Alternatively, a PC’s USB port may be used with a USB-to-Serial adapter and appropriate driver software. These devices are available from several manufacturers.
The COM port supports a serial data rate of 1200-115200 bps (115200 default, asynchronous only). The unit is hardwired as a DCE device. Supported data formats for the COM port are:
8N1 - 8 char bits, no parity, 1 stop bit (Default setting) 8N2 - 8 char bits, no parity, 2 stop bits 8O1 - 8 char bits, odd parity, 1 stop bit 8O2 - 8 char bits, odd parity, 2 stop bits 8E1 - 8 char bits, even parity, 1 stop bit 8E2 - 8 char bits, even parity, 2 stop bits 7N1 - 7 char bits, no parity, 1 stop bit 7N2 - 7 char bits, no parity, 2 stop bits 7O1 - 7 char bits, odd parity, 1 stop bit 7O2 - 7 char bits, odd parity, 2 stop bits 7E1 - 7 char bits, even parity, 1 stop bit 7E2 - 7 char bits, even parity, 2 stop bits.
The tables below provide pin descriptions for the COM1 data port in RS-232 mode and RS-485 modes, respectively.
NOTE: The COM2 port, if present, is restricted to RS-232 mode; it cannot be used for RS-485.
(As viewed from the outside of the unit)
Table 2. COM1/2 Port Pin Details (RS-232)
Pin Number
1 Reserved 2 3 Reserved 4 Ground Connects to ground (negative supply potential) on chassis
Input/Output Pin Description
OUT DCD (Data Carrier Detect)
6 MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C
Table 2. COM1/2 Port Pin Details (RS-232) (Continued)
Pin Number
5 6 7 8
Input/Output Pin Description
OUT RXD (Received Data)—Supplies received data to the connected device IN TXD (Transmitted Data)—Accepts TX data from the connected device OUT CTS (Clear to Send) IN RTS (Ready to Send)
Table 3. COM1 Port Pin Details (RS-485)
Pin Number
1 Reserved 2 3 Reserved 4 Ground Connects to ground (negative supply potential) on chassis 5 OUT TXD+ (Transmitted Data +)—Non-inverting driver output. Su pplies
6 IN RXD+ (Received Data +)— Non-inverting receiver input. Accepts
Input/Output Pin Description
OUT DCD (Data Carrier Detect)
received payload data to the connected device.
payload data from the connected device. 7 OUT TXD-/TXB (Transmitted Data -)—Inverting driver output 8 IN RXD-/RXB (Received Data -)— Inverting receiver input
COM1 Port notes and wiring arrangements (RS-485):
The COM1 port supports 4-wire and 2-wire RS-485 mode.
· RXD+ / RXB and RXD– / RXA are data sent into the unit
· RXD+ / RXB is positive with respect to RXD– / RXA when the line input is a “0”
· TXD+ / TXB and TXD– / TXA are data sent out by the unit
· TXD+ / TXB is positive with respect to the TXD– / TXA when the line output is a “0”
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual 7
Cell Antennas (AUX and MAIN)—These SMA coaxial connectors are for attachment of cellular antennas. The MAIN connection is for basic cellular transmission/reception, and the AUX connector is for attachment of a receive-only antenna which provides MIMO receive operation (diversity) with standard 4G modules, improving signal quality in many installations. In general, both antennas should always be used for cellular operation. The GE MDS part number for this antenna type is 97-2485A04.
Figure 5. Directly-Connected Cellular Antenna (Typical Style)
(GE MDS Part No. 97-2485A04)
WiFi Antenna—Antenna connection for 2.4 GHz WiFi service. The connector appears similar to the cel­lular connectors discussed above, but is a Reverse-SMA type. It contains a pin that matches with an SMA-F connector. The GE MDS part number for this antenna is 97-4278A48.
SIM Port—This port accepts a mini SIM card (2FF type) for 4G cell operation. The unit’s cellular interface will not function without a valid SIM card installed. The customer is responsible for obtaining a provisioned SIM card for the appropriate service plan from their cellular provider. module’s IMSI/IMEI (typically required for provisioning) is provided on Page 35 of this manual.
CAUTION: Do not insert the SIM card when the unit is powered on.
Card Insertion: The SIM card only inserts one way; do not force it. It should be inserted with the printed label facing up, and the cut-off corner on the left side (see Figure 6). This side is inserted first. A small instrument, such as a flathead screwdriver, may be helpful to gently push the SIM all the way in until it locks.
Information on determining the cell
Invisible place holder
Figure 6. Steps for Inserting the SIM Card
8 MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C
LED Status Indicators—The LEDs on the unit provide visual indications of the status of the device as shown in Figure 7 and explained in Table 4 which follows.
Figure 7. LED Status Indicators
Table 4. Description of LED Status Indicators
LED Name LED State Description
PWR
(DC Power)
ETH
(Ethernet)
COM
(Serial Comm. Port)
NIC1
(Cell)
Off Solid Green Fast Blink/Red (1x/sec.)
Off Solid Green Blinking Green
Off Blinking Green
Off Solid Green
No power to unit Unit is powered, no problems detected Alarm indication
No Ethernet link to network Ethernet link present Ethernet traffic in/out
No serial connection, or idle Serial traffic in/out
No cellular connection Cell Connection
NIC2
(WiFi)
Access Point Mode Solid Green
Station Mode Off
Off Interface disabled
Operating as AP and at least one client connection
Solid Red
Solid Green
Operating as an AP and no client connection No connection
Wi-Fi connection established.
NOTE: In addition to the LEDs above, the Ethernet connector has two embedded LEDs. A yellow indi-
cates a link at 100 Mbps operation. A flashing green indicates Ethernet data traffic.

2.4.1 Grounding Considerations

To minimize the chance of damage to the unit and its connected equipment, a safety ground (NEC Class 2 compliant) is recommended, which bonds the chassis, antenna system(s), power supply, and connected data equipment to a single-point ground, keeping all ground leads as short as pos­sible.
Normally, the unit is adequately grounded if mounted with the flat brackets to a well-grounded metal surface. If the unit is not mounted to a grounded surface, it is recommended that a safety ground wire be attached to the screw provided on the bottom corner of the enclosure, in the recessed flat area. Alternatively, a safety ground wire may be attached to one of the mounting bracket screws.
The use of a lightning protector is recommended where the antenna cable enters the building; Bond the protector to the tower ground, if possible. All grounds and cabling must comply with applicable codes and regulations. One source for lightning protection products may be found online at http://www.protectiongroup.com/PolyPhaser.
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual 9

2.4.2 Mounting Options

8.5 (21.59 cm)
9.25 (23.5 cm)
4.81 (12.22 cm)
The unit may be mounted with flat mounting brackets or an optional 35 mm DIN rail attachment.
Figure 8 shows the mounting dimensions for a unit equipped with flat mounting brackets.
Invisible place holder
Figure 8. Flat Mounting Bracket Dimensions
NOTE: To prevent moisture from entering the unit, do not mount the case with the cable connectors
pointing up. Also, dress all cables to prevent moisture from running along the cables and into the unit.

2.4.3 Optional DIN Rail Mounting

If ordered with the DIN rail mounting option, the unit is supplied with a DIN rail clip attached to the case. The integrated bracket on the unit’s case allows for quick installation and removal from a DIN mounting rail as shown in Figure 9.
Figure 9. DIN Rail Attachment and Removal
(Pull down tab to release from rail)
10 MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C

2.4.4 Antenna Planning & Installation

Consideration must be taken to select appropriate antennas for optimal RF performance. This section reviews the key factors involved in selecting and installing antennas for the MCR-4G. Only approved antennas may be used on the unit's RF output connectors, as listed in Table 5. The use of non-approved antennas may result in a violation of FCC rules, and subject the user to FCC enforcement action.
Table 5. Approved Antenna Types
Antenna Application GE MDS Part Number
WiFi (direct connect), RP SMA,
2.4-2.5 GHz Antenna, 3.2dBi Gain WiFi (external mount), Omni Ant. N M
Term., 2.4-2.5 GHz, 2 dBi Gain Cell (direct connect), 960/2170/2700MHz 97-2485A04 Cell (external mount, ground plane),
960/2170/2700MHz, requires ground WiFi (Magnetic Mount) 5 ft./1.52 m Cable,
RP SMA Plug

Antenna Type and Orientation

It is important to use antennas designed to operate in the applicable cellular coverage bands with a Return Loss of 10 dB or better. Placement of the antennas also plays a key role in the coverage of the system. While the antennas can be placed directly on the face of the unit in some short range installations, the best perfor­mance is obtained when mounting antennas remotely using low loss coaxial cable. Antennas mounted in close proximity to each other can couple signals between them and desensitize the RF module.
97-4278A34
97-4278A48
97-2485A05
97-4278A78
When placing the indoor SMA style “paddle” antennas on the face of the unit, position them with a 90 degree angle of separation to improve the isolation. A “V” or an “L” configuration is a common approach to use with the Main channel typically mounted for vertical polarization. The multipath nature of Cellular systems means that polarization for indoor use is not normally a critical factor. Isolation between the antennas is more important.
Note that with any installation, there needs to be a minimum 20 cm spacing between the Wi-Fi antenna and any other radio antenna to avoid co-location difficulties.
Indoor use case:
1. This scenario employs direct mounting of an LTE paddle antenna (GE MDS PN: 97-2485A04) on the Main and Aux Cell channels, and cabled mounting of the Wi-Fi antenna (GE MDS PN: 97-4278A34) using a magnetic mount (GE MDS PN: 97-4278A78). This configuration offers easy mobility for evaluation purposes or indoor applications with good cellular signal coverage (see Figure 10).
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual 11
Figure 10. Direct Mounting of Cell Antenna; Cabled WiFi Antenna
Minimum 8-inch (20.32 cm) separation between cell and WiFi antennas
2. This arrangement employs cabled mounting of the L TE paddle antennas (GE MDS 97-2485A04) o n the Main and AUX Cell channels, and cabled mounting of the Wi-Fi antenna (GE MDS 97-4278A34) using a magnetic mount (GE MDS 97-4278A78). The Wi-Fi antenna may also be directly attached to the unit if desired. This configuration works well for indoor installations in equipment closets, or for more permanent applications.
Outdoor use case:
External enclosures—If the system is going to be installed in a weathertight enclosure and mounted outside in the elements, cabled use of external LTE antennas (GE MDS PN: 97-2485A05) on the Main and AUX Cell ports, with cabled use of the External Wi-Fi antenna (GE MDS PN: 97-4278A48) is a good solution. This configuration requires a suitable metallic ground plane for the Cellular antennas (8" diameter disc min­imum for the 97-2485A05 series) or a suitable counterpoise for frequencies as low as 698 MHz. Metal enclosures work well for ground plane requirements when ground contact inside the box is not impeded by painted surfaces.
Do not use internally mounted antennas inside of metal enclosures. Other antenna configurations can be easily customized for applications not listed here. Consult your factory
representative for installation matters.
12 MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C

2.4.5 Accessories and Spares

Table 6 lists common accessories and spare items for use with the MCR-4G. GE MDS also offers an Acces-
sories Selection Guide listing an array of additional items that may be used with the product. Contact your
factory representative or visit
Item Description Part Number
DC Power Plug, 2-pin, polarized Mates with power connector on the
Setup Guide (for installation instructions)
Flat Mounting Bracket Kit Bra ckets that attach to the bottom of
COM Port Adapter Converts the unit’s RJ-45 serial jack
www.gemds.com to obtain a copy of the guide.
Table 6. Accessories & Ancillary Items
unit’s case. Screw terminals are provided for wires, threaded locking screws to prevent accidental disconnect.
Describes the installation and setup of the unit. It is a companion to this Technical Manual. PDF copy available free at www.gemds.com.
the unit. Used for mounting to a flat mounting surface.
to a DB-9F type.
73-1194A53
05-6702A01
03-4123A14
73-2434A12
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual 13

3.0 DEVICE MANAGEMENT

This section describes the steps for connecting a PC, logging in, and setting unit parameters. The focus here is on the local serial console interface, but other methods of connection are available and offer similar capa­bilities. The key differences are with initial access and appearance of data.
The MCR offers several interfaces to allow device configuration and monitoring of status and performance. These include local serial console, USB, NETCONF, HTTPS, and Secure Shell (SSH) for local and remote access via the WAN and LAN networks. The serial console, USB, and SSH services offer a command line interface (CLI). There are three user accounts/roles for management access: accounts can be centrally managed with a RADIUS server. RADIUS accounts can be mapped to one of the three user accounts/roles (see see “RADIUS” on Page 71).
NOTE: The Orbit MCR device is designed for high security environments. As such, management of the
device does not support Telnet, but instead implements the more secure SSH protocol.

Web-Based Device Manager

A web-based user interface is also available fo r this product. The web interface provides an intuitive, graph­ical facility, well-suited for many simple routine configuration and control tasks. An introduction and sample screens for the web interface are provided in “APPENDIX G – Device Manager” on Page 129.

3.1 Connecting to a PC

3.1.1 Differences Between Serial & SSH

admin, tech, and oper. User
Serial and SSH both present identical management capabilities, but the method of access is dif­ferent for each. Serial involves an RS-232 serial connection from a PC to the unit’s management COM port. SSH uses an Ethernet PC connection to the unit’s ETH port. Maximum recommended cable length for a serial connection is 50 feet (15 meters). SSH can be connected to the unit from any network point that has connectivity with the PC, including remotely over the Internet, or using other networks.
The focus of these instructions is on Serial access, but SSH may also be used by following these additional points, which replace Steps 1-3 below:
• Connect to the unit with a PC that is on the same IP network as the MCR. Launch an SSH client program, and connect to the unit using its programmed IP address.
• The default IP address for the unit is 192.168.1.1. If you do not know the current IP address of the unit, follow the serial configuration instructions below, where you can determine the address and continue configuration, or check with your network administrator.

3.1.2 Establishing Communication—Serial Interface

Follow these steps to configure the unit for its first use with serial console interface:
1. Connect a PC to the unit’s
COM port as shown in Figure 11. (Maximum recommended cable
length: 50 ft./15 m)
NOTE: Not all PCs include a serial port. If one is not available, a USB port may be used, along with a USB-to-Serial
adapter (with appropriate driver software). Adapters are available from many manufacturers, including GE MDS. The MCR Orbit’s USB port can be used to access the device management console by using a Mini-USB cable between the device and a PC. The PC needs to register the device driver.
14 MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C
NOTE: If the COM port has been configured for terminal server operation, pressing +++ switches it to console
PC Running Terminal Session
To COM Port
ENTER
ENTER
ENTER
(management) mode. Serial console mode is required for the following steps.
Launch a terminal communications program, such as HyperTerminal with the following commu­nication parameters: 1 15200 bps (default speed), 8 bits, no parity, one stop bit (8N1), and flow control disabled. Incorrect parameter settings are a frequent cause of connection difficulties; Double check to be sure they are correct.
If necessary, an adapter may be used to convert the unit’s RJ-45 serial jack to a DB-9F type (GE MDS part no. 73-2434A12). If no serial port exist on the PC, a USB-to-serial adapter cable may be used to connect to the MCR unit, or a Mini-USB cable may be connected between the MCR’s USB device port and the PC.
Invisible place holder
Figure 11. PC Connection for Programming/Management
2. Press the key to receive the Login: prompt. This indicates that the unit is ready to receive commands.
3. At the Login: prompt, enter admin (lower case) and press .
4. If no password has been previously set, enter the default password (admin) and press ; Otherwise, enter the saved password at the Password: prompt. (Before placing the unit in final service, it is recommended that the default password be changed to ensure that only authorized users have access.)
5. After successful login, the command prompt appears where you may configure and manage a number of unit settings.

3.1.3 Setting Basic Parameters—First Steps

There are three tasks that should be performed after initial startup and connection to a PC, as follows:
1. Create One-Time Programmable passwords for device recovery in the event a password is lost.
2. Change the login passwords.
3. Evaluate the default factory configuration and set it to the user's required security level.

Tab Completion Feature

Tab-completion is a powerful feature that presents CLI users with assistance while typing. Depending on the text that was already entered, tab-completion will display different possible completions. When the tab key is pressed and no text has been entered, the CLI shows all possible commands that can be typed.
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual 15

3.1.4 One-Time “Recovery” Passwords

The MDS Orbit platform employs extensive security measures to prevent unauthorized access. As such, there are no hidden manufacturer passwords or other “backdoors” found in less secure products. If a pass­word is lost, there is no way to access the unit, except by using a one-time password (OTP) for recovery. This must be established by the user beforehand. Without a one-time password, the unit will not be acces­sible, and the hardware will need to be replaced. Not even the factory will be able to assist you if a password
is lost, so creating a one-time password is strongly encouraged.

One-Time Passwords: How They Work

One-time recovery passwords put control directly and exclusively in the user’s hands. They are similar to spare keys for a lock. If you make a spare key, and put it away safely, you can take it out to quickly gain entry when your primary key is lost. If you don’t make a spare, you are always at risk of locking yourself out.
A one-time recovery password is different from the one used to log into the unit on a routine basis. It is only for use when the primary password is lost or forgotten. When a one-time password is used to log in, that password is automatically revoked from the list of passwords created. (You may create up to five one-time passwords at one time, and more can be created if some get used). A password cannot be used ag ain for log-in to the unit (hence the name “one-time” password).

Creating a One-Time Password

To create a one-time recovery password, proceed as follows:
1. Upon successful log-in, enter the following command:
request system recovery one-time-passwords create function <selected function>
A one-time password is automatically generated and displayed on the screen. Copy this password and save it in the desired location on your PC. There is no way to ever view it again from the
command line console, so be sure it is properly saved.
2. To create additional one-time passwords (up to a total of five), repeat the step above.

Logging in With a One-Time Password

Logging in with a one-time password can only be performed from the local serial or USB cons ole. You cannot use a one-time password when connecting to the unit remotely. To use the one-time password for log-in, proceed as follows:
1. At the username prompt, enter the word
2. At the
password prompt, paste in the one-time-password saved earlier on your PC. Using a
recovery.
one-time-password forces the unit to perform the “function” which was previously defined when the password was created:
factory-reset—The unit resets its entire configuration to factory defaults
login—The unit allows logging in with “admin” privileges
Special case: If someone has disabled console access on the
COM port, the login prompt will still be present
on that console, but only one-time-passwords will be accepted. This is done to provide a way to recover the unit in the case where the
COM port has been disabled and the unit cannot be accessed via TCP (for example;
SSH).

Deleting a One-Time Password

As noted earlier, a one-time password is automatically revoked when it is used for log-in. A revoked pass­word may be replaced, but it must first be removed from the list so a new one can be generated. Any of the five stored passwords may be removed on demand. As long as there is a free slot, an additional password can be created, up to the maximum number of five. Logs are generated when the user creates, deletes or logs in with a one-time-password. To remove an existing password from the list, proceed as follows:
16 MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C
Enter the command request system recovery one-time-passwords delete identifier X, where X is a number
from the currently available one-time passwords. This identifier is not reused. If all five passwords have been created, then ID 1 can be deleted, and the next created password will be at ID 6.
The current list of passwords may be viewed by issuing the command
. The following is an example output from that command. On the unit shown, only two passwords
words
show system recovery one-time-pass-
have been stored. Password 1 or 2 can be deleted from this list.
DATE
IDENTIFIER FUNCTION STATUS DATE CREATED REVOKED USER
----------------------------------------------------------------------
1 login usable 2012-06-19T00:27:24+00:00 2 login usable 2012-06-19T00:27:25+00:00
3.2 Pre-Configured Settings
The MCR is highly configurable to meet field requirements, but comes pre-configured as follows:
• The COM and USB ports are enabled for local console operation
• The Ethernet ports are bridged with the WiFi AP
• WiFi AP SSID is set based on the unit's serial number, and takes the form of:
GEMDS_<SERNUM>. The unit’s serial number is printed on the chassis sticker.
• WiFi is enabled with passphrase:
• A DHCP server is enabled for WiFi clients and the Ethernet LAN ports
• Cellular service is enabled with firewall/router rules in place.
• The following default configured firewall rules are also in effect:
# Firewall
set services firewall enabled true set services firewall address-set LOCAL-NETS addresses [ 192.168.1.0/24 ] set services firewall filter IN_TRUSTED rule 10 match protocol all set services firewall filter IN_TRUSTED rule 10 actions action accept set services firewall filter IN_UNTRUSTED rule 1 match protocol icmp set services firewall filter IN_UNTRUSTED rule 1 actions action accept set services firewall filter IN_UNTRUSTED rule 2 match protocol udp set services firewall filter IN_UNTRUSTED rule 2 match src-port services [ dns ] set services firewall filter IN_UNTRUSTED rule 10 match protocol all set services firewall filter IN_UNTRUSTED rule 10 actions action drop set services firewall filter OUT_TRUSTED rule 10 match protocol all set services firewall filter OUT_TRUSTED rule 10 actions action accept set services firewall filter OUT_UNTRUSTED rule 1 match src-address address-set LOCAL-NETS set services firewall filter OUT_UNTRUSTED rule 1 match src-address add-interface-address true set services firewall filter OUT_UNTRUSTED rule 10 match protocol all set services firewall filter OUT_UNTRUSTED rule 10 actions action drop set services firewall nat source rule-set MASQ rule 1 source-nat interface
GEMDS_ORBIT
The commands below show how the default settings are made. The unit must be in Configuration Mode to make these settings. Each command string begins with the word
1. set interfaces interface Wi-Fi physical-interface Wi-Fi
2. set interfaces interface Wi-Fi wifi-config mode access-point ap-config ap GEMDS_1 broadcast-ssid true privacy-mode wpa2-personal psk-config psk GEMDS_ORBIT
3. set interfaces interface Cell physical-interface Cell
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual 17
set:
4. set interfaces interface Cell ipv4 dhcp
5. set interfaces interface Cell filter in put IN_UNTRUSTED
6. set interfaces interface Cell filter ou tput OUT_UNTRUSTED
7. set interfaces interface Cell nat source MASQ
8. set services serial console serial-ports [ COM1 USB1 ]
9. set interfaces interface ETH1 ph ysical-interface ETH1
10. set interfaces interface ETH2 physical-interface ETH2
11. set interfaces interface Bridge virtual-type bridge
12. set interfaces interface Bridge filter input IN_TRUSTED
13. set interfaces interface Bridge filter output OUT_TRUSTED
14. set interfaces interface Bridge ipv4 address 192.168.1.1 prefix-length 24
15. set interfaces interface Bridge bridge-settings members port ETH1
16. set interfaces interface Bridge bridge-settings members port ETH2
17. set interfaces interface Bridge bridge-settings members wifi-ap GEMDS_1
18. set services dhcp v4subnet 192.168.1.0/24 range-start 192.168.1.2 range- end 192.168.1.10 broad­cast-address 192.168.1.255 router 192.168.1.1
19. set services dhcp enabled true
3.3 YANG Interface
The unit employs a data modeling language called YANG to model the configuration and status of the device. YANG is used in conjunction with the NETCONF protocol to provide a device-specific data model that can be administered by any NETCONF-capable NMS. The YANG data model is released with each version of the device so NMS administrators can accurately administer the device per release.
Together, YANG and NETCONF present a structured user interface for the unit. The device data defined by the YANG data model is either Operational Data or Configuration Data. Configuration Data may be changed, but Operational Data can only be viewed.

Configuration Data

Configuration Data is any piece of data that can be changed by an administrator and the changes are persis­tent even if the device reboots. The IP address of the LAN port is an example of Configuration Data.

Operational Data

Operational Data is any piece of data that is volatile and will not be saved if the device is rebooted. Opera­tional data is typically read-only, such as statistics information showing status or a value representing the operation of the device. Ethernet statistics are an example of operational data.

Default Values

While configuring the unit, some of the configuration data may not need to be explicitly set, but instead the data assumes the default value defined in the data model. For example, when a File Server configuration is added and the server type is specified as TFTP, then the remote TFTP port will default to
69 if the user does
not explicitly specify the port. Data nodes that do not have a default value will require entry of a value for that node during configuration. The command line interface (CLI) prompts for entry of a node value if the node is mandatory and does not have a default value.
18 MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C
When viewing the configuration, the nodes that have default values and have not been explicitly set by the user are not displayed. Users can selectively view these defaulted values by using The
show command can be used to view configuration data. Notice that the information displayed is dif-
details option on the CLI.
ferent, depending on which mode the CLI is in; Operational or Configuration.

Remote Procedure Call (Request)

This is an action that a user requests. Rebooting of the device, for example, is considered a request.

Privilege

A user who logs on to the device will belong to a role-based group. Each group is limited in capability to view operational data or to change configuration data. Groups with lesser privileges will not be presented with the option to view or change data on the CLI, which can be done by higher-privileged groups.

Changing Configuration Data and committing changes

Changing configuration data requires two steps. The first step is to use a user-interface to add, remove, or alter a piece of configuration data. The second step is to use the user-interface to commit the change. Mul­tiple changes can be made prior to committing them. This two-step process allows users to make multiple changes to the configuration and apply them in a bulk commit. Additionally, the device can validate the bulk commit and reject it if there is an error.

3.3.1 CLI Login Prompt

The CLI is available via the serial console or an SSH session. Use the default serial console settings shown in the section titled “Serial Console” on Page 26 to connect a Computer to the unit via a serial cable. Once the network settings are configured, users can also connect to the device via SSH over the network.
The CLI prompts for a login to the device before any other actions can be made. The defaults for both user­name and password are
admin. These credentials should be changed before placing the unit in full service.
(none) login: admin Password: (valid password, default is admin) Welcome to the CLI admin connected from 127.0.0.1 using console on (none)
admin@(none) 04:24:12>

Using the CLI

This section describes how to use the CLI by using an example: changing the name of the unit. Step 1: Login to the device using the serial console and us e the default username admin and the default pass-
admin.
word
(none) login: admin Password: Welcome to the CLI admin connected from 127.0.0.1 using console on (none)
admin@(none) 04:24:12>
Step 2: Instruct the device to enter configuration mode by typing configure and pressing the enter key:
admin@(none) 04:51:06> configure Entering configuration mode private [ok][2012-06-20 04:51:07] [edit] admin@(none) 04:51:07%
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual 19
Step 3: Change the device name by typing in the following, followed by enter: set system name Device539
admin@(none) 05:31:14% set system name Device539 [ok][2012-06-20 05:32:45] [edit] admin@(none) 05:32:45%
Step 4: Verify the change looks correct by reading the data back using the following, followed by the enter
show system name
key:
admin@(none) 05:32:53% show system name name Device539; [ok][2012-06-20 05:35:28] [edit] admin@(none) 05:35:28%
Step 5: Commit the change by typing in the following, followed by the enter key: commit
admin@(none) 05:36:20% commit Commit complete. [ok][2012-06-20 05:36:21] [edit] admin@Device539 05:36:21%
Step 6: Exit the configuration mode by typing the following, followed by the enter key: exit
admin@Device539 05:40:15% exit [ok][2012-06-20 05:40:17] admin@Device539 05:40:17>
Step 7: Exit the login session by typing the following, followed by the enter key: exit
admin@Device539 05:40:32> exit Device539 login:
20 MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C
CLI Quick Reference Table
Table 7 provides a summary listing of commonly-needed tasks and the appropriate commands to enter. The
table can be used as a quick reference before consulting the more detailed information which follows in this section. Each CLI command is proceeded by the symbol
> for operational command, or % for a configura-
tion command.
Table 7. CLI Quick Reference Table
If you wish to... Enter this CLI command:
Create a one-time password > request system recovery one-time-password create function <user
function>
View all network interface status and statistics
Create a bridge % set interfaces interface myBridge virtual-type bridge Add the ETH1 interface to a
bridge Remove the ETH1 interface
from a bridge Set WiFi AP SSID % set interfaces interface Wi-Fi wifi-config mode access-p oint
Enable WiFi WPA2-Personal security
Enable WiFi SSID Broadcasting
View WiFi settings > show configuration interfaces interface Wi-Fi wifi-config | details Monitor WiFi statistics > show interfaces interface Wi-Fi statistics | repeat 5 View the cell module status > show interfaces interface Cell View the cell APN > show configuration interfaces interface Cell cell-config apn View the routing table > show routing View the event log > show table logging event-log Set the admin user’s
password Set the device name % set system name “Mydevice” Set the baud rate on COM1 % set services serial ports COM1 baud-rate b19200 Download a firmware
package from TFTP server at
192.168.1.10 Monitor firmware download
status Export configuration file to a
TFTP server at 192.168.1.10 Reboot device to firmware
image #2
> show interfaces
% set interfaces interface myBridge bridge-settings members port ETH1
% delete interfaces interface myBridge bridge-settings members port ETH1
ap-config ap myssid % set interfaces interface Wi-Fi wifi-config mode access-p oint
ap-config ap myssid privacy-mode wpa2-personal psk-config psk mypassphrase encryption ccmp
% set interfaces interface Wi-Fi wifi-config ap-config ap myssid broadcast-ssid true
> request system authentication change-password user admin password admin1234
> request system firmware reprogram-inactive-image filename iwc-bkrc-1_0_0.mpk manual-file-server { tftp { address 192.168.1.10 } }
> show system firmware reprogramming-status
> request system configuration-files export filename myConfig.txt manual-file-server {tftp {address 192.168.1.10} }
> request system power restart-to-image location 2
MDS 05-6628A01, Rev. C MDS Orbit MCR Technical Manual 21

Specific Examples

Example #1
In Figure 12, the MCR-4G is functioning as a WiFi Access Point to provide connectivity between a set of laptops and a handheld device. The MCR-4G is also acting as a DHCP server for the laptops and handheld device.
Invisible place holder
Figure 12. Example 1: Unit Providing Laptop and Handheld Device Connectivity
The following commands will configure the MCR-4G for this scenario.
1. % set interfaces inter fa ce Wi-Fi physical-interface Wi-Fi
2. % set interfaces inter fa ce Wi-Fi wifi-config mode access-point ap-config ap myssid enabled true
3. % set interfaces inter fa ce myBridge virtual-type bridge
4. % set interfaces inter fa ce myBridge bridge-settings members port ETH1
5. % set interfaces inter fa ce myBridge bridge-settings members wifi-ap myssid
6. % set interfaces inter fa ce myBridge ipv4 address 192.168.1.21 prefix-length 24
7. % set services dhcp enabled true v4subnet 192.168.1.0/24 domain-name gemds range-start 192.168.1.10
range-end 192.168.1.19 router 192.168.1.1 broadcast-address 192.168.1.255
22 MDS Orbit MCR Technical Manual MDS 05-6628A01, Rev. C
Loading...
+ 122 hidden pages