Lantronix EDS-MD Series Installation manual

Part Number 900-592
Revision D September 2019
EDS-MD
Wired IoT Gateway for Medical Devices
Command Reference
EDS-MD 4
EDS-MD 8
EDS-MD 16

EDS-MD® Wired IoT Device Gateway Command Reference 2
Intellectual Property
© 2019 Lantronix, Inc. All rights reserved. No part of the contents of this book may be transmitted
or reproduced in any form or by any means without the written permission of Lantronix.
Lantronix, EDS-MD, MACH10, and TruPort are registered trademarks of Lantronix, Inc. in the
United States and other countries. DeviceInstaller and Com Port Redirector are trademarks of
Lantronix, Inc.
Patented: patents.lantronix.com; additional patents pending
Windows is a registered trademark of Microsoft Corporation. All other trademarks and trade
names are the property of their respective holders.
Contacts
Lantronix, Inc.
7535 Irvine Center Drive
Suite 100
Irvine, CA 92618, USA
Toll Free: 800-526-8766
Phone: [phone]
Fax: [phone]
Technical Support
Online: www.lantronix.com/support
Sales Offices
For a current list of our domestic and international sales offices, go to the Lantronix web site at
www.lantronix.com/about/contact.
Disclaimer
All information contained herein is provided “AS IS.” Lantronix undertakes no obligation to
update the information in this publication. Lantronix does not make, and specifically disclaims,
all warranties of any kind (express, implied or otherwise) regarding title, non-infringement, fitness,
quality, accuracy, completeness, usefulness, suitability or performance of the information provided
herein. Lantronix shall have no liability whatsoever to any user for any damages, losses and
causes of action (whether in contract or in tort or otherwise) in connection with the user’s access or
usage of any of the information or content contained herein. The information and specifications
contained in this document are subject to change without notice.
The EDS-MD wired IoT device gateway is not a medical device as such term is defined in the U.S.
Food, Drug and Cosmetic Act, as amended, and is not subject to regulation by the U.S. Food and
Drug Administration (FDA).

EDS-MD® Wired IoT Device Gateway Command Reference 3
Revision History
Date Revision Comments
September 2011 A Initial Document. Created for the 7.2.0.0 release.
April 2015 B Updated to firmware release 7.2.0.3.
May 2019 C Updated to firmware release 8.1.0.3 which includes the addition of the
following:
Gateway port forwarding, static routes and DHCP server
Support for NTP in clock
Support for Action settings
Ethernet ports work separately
Support for MACH10 client
September 2019 D Updated to firmware release 8.1.0.4.

EDS-MD® Wired IoT Device Gateway Command Reference 4
Table of Contents
Intellectual Property ________________________________________________________2
Contacts _________________________________________________________________2
Disclaimer ________________________________________________________________2
List of Figures _____________________________________________________________5
List of Tables ______________________________________________________________6
1: About This Guide 7
Chapter Summaries ________________________________________________________7
Conventions ______________________________________________________________7
Additional Documentation ____________________________________________________8
2: Overview 9
XML Architecture and Device Control ___________________________________________9
Command Line Interface _____________________________________________________9
3: Command Line Interface 10
Configuration Using Telnet __________________________________________________10
Configuration Using Serial Lines ______________________________________________10
Boot to CLI and Device Recovery _________________________________________11
Navigating the CLI Hierarchy ________________________________________________11
Using Keyboard Shortcuts and CLI ____________________________________________12
Understanding the CLI Level Hierarchy ________________________________________12
4: Configuration Using XML 15
XML Configuration Record Document Type Definition _____________________________15
Quick Tour of XML Syntax __________________________________________________16
Declaration ___________________________________________________________16
Element Start and End Tags _____________________________________________16
Element Attributes _____________________________________________________16
Record, Group, Item, and Value Tags _________________________________________17
Importing and Exporting an XML Configuration File _______________________________19
Best Practices ____________________________________________________________19
Importing _____________________________________________________________19
Exporting ____________________________________________________________20
XML Configuration Groups __________________________________________________21
XML Status Record Groups and Items _________________________________________35
5: Commands and Levels 44

EDS-MD® Wired IoT Device Gateway Command Reference 5
List of Figures
Figure 3-2 CLI Level Hierarchy ______________________________________________________13
Figure 3-3 Login Level Commands___________________________________________________13
Figure 3-4 Enable Level Commands__________________________________________________14
Figure 4-1 DTD for XCRs __________________________________________________________15
Figure 4-2 XML Example __________________________________________________________16
Figure 4-3 XML Example __________________________________________________________17
Figure 4-4 XML Example of Multiple Named Values _____________________________________17
Figure 4-5 XML Example of Multiple Items _____________________________________________18
Figure 4-6 XML Example with Multiple Groups__________________________________________18

EDS-MD® Wired IoT Device Gateway Command Reference 6
List of Tables
Table 3-1 Keyboard Shortcuts ______________________________________________________12
Table 4-7 XCR Groups ____________________________________________________________21
Table 4-8 XSR Group and Items ____________________________________________________35
Table 5-9 Commands and Levels ___________________________________________________54

EDS-MD® Wired IoT Device Gateway Command Reference 7
1: About This Guide
This guide describes how to configure the Lantronix® EDS-MD® wired IoT device gateway using
the Command Line Interface (CLI) and/or Extensible Markup Language (XML). CLI provides an
interactive mode for accessing the device configuration and management interface. It is most
suited for system and network administrators comfortable with using similar interfaces on
Enterprise IT and Networking products. It is also helpful as a quick tool for access via the
product's serial ports or console/management ports.
XML provides an extensible mode for software developers interfacing with the device and system
integrators performing batch provisioning/updates.
Note: EDS-MD wired IoT device gateways (which include models EDS-MD 4, EDS-MD
8 and EDS-MD 16) are commonly referred to as either EDS-MD 4/8/16 or as EDS-MD
when mentioned within a description equally applicable to any of the three models.
Chapter Summaries
This table lists and summarizes content of each chapter.
Conventions
The table below lists and describes the conventions used in this book.
Chapter Summary
Chapter 2: Overview Gives an overview of CLI and XML.
Chapter 3: Command Line Interface Lists commands and describes how to use CLI to configure the
EDS-MD 4/8/16 wired IoT device gateways.
Chapter 4: Configuration Using XML Lists XCR groups and items and describes how to use XCRs to
configure the EDS-MD 4/8/16 wired IoT device gateways.
Chapter 5: Commands and Levels Provides an index of the CLI Command Hierarchy with hyperlinks
to the corresponding command details.
Convention Description
Bold text Default parameters.
Italic text Required values for parameters
Brackets [ ] Optional parameters.
Angle Brackets < > Possible values for parameters.
Pipe | Choice of parameters.
Warning Warning: Means that you are in a situation that could cause
equipment damage or bodily injury. Before you work on any
equipment, you must be aware of the hazards involved with electrical
circuitry and familiar with standard practices for preventing accidents.
Note Note: Means take notice. Notes contain helpful suggestions, information,
or references to material not covered in the publication.

1: About This Guide
EDS-MD® Wired IoT Device Gateway Command Reference 8
Additional Documentation
Visit the Lantronix website at www.lantronix.com/resources/product-index/ for the latest
documentation and the following additional documentation.
Caution Caution: Means you might do something that could result in faulty
equipment operation, or loss of data.
Screen Font
(Courier New)
CLI terminal sessions and examples of CLI input.
Document Description
EDS-MD Wired IoT Device Gateway
User Guide
Describes how to configure and use an EDS-MD 4/8/16 wired IoT
device gateway.
Com Port Redirector
Quick Start and Online Help
Instructions for using the Lantronix Windows based utility to create
virtual com ports.
Lantronix Provisioning Manager
User Guide
Instructions for using Lantronix Provisioning Manager to discover,
configure, upgrade, and manage an EDS-MD 4/8/16 wired IoT
device gateway.
Convention (continued) Description

EDS-MD® Wired IoT Device Gateway Command Reference 9
2: Overview
The EDS-MD 4, EDS-MD 8 and EDS-MD 16 wired IoT device gateways support three convenient
configuration methods: Web Manager, Command Line Interface (CLI) and Extensible Markup
Language (XML). For more information about the Web Manager, see the EDS-MD Wired IoT
Device Gateway User Guide on the Lantronix website.
XML Architecture and Device Control
XML is a fundamental building block for Machine-to-Machine (M2M) and Internet of Things (IoT)
networks. The EDS-MD 4/8/16 wired IoT device gateway supports XML configuration records that
make configuring the wired IoT device gateway easy for users and administrators. XML
configuration records are easy to edit with a standard text editor or an XML editor.
For a brief overview of XML, see Chapter 4: Configuration Using XML. It provides rules on basic
XML syntax, a guide to the specific XML tags used, and a guide to using XML configuration
records.
Command Line Interface
The EDS-MD 4/8/16 wired IoT device gateway uses industry-standard tools for configuration,
communication, and control. For example, the EDS-MD 4/8/16 wired IoT device gateway uses a
command line interface (CLI) whose syntax is very similar to that used by data center equipment
such as routers and hubs.
For details of the CLI, see Chapter 5: Commands and Levels. It provides an index of the CLI
Command Hierarchy with links to the corresponding command details. The CLI provides
commands for configuring, monitoring, and controlling the wired IoT device gateway.

EDS-MD® Wired IoT Device Gateway Command Reference 10
3: Command Line Interface
This chapter describes accessing the EDS-MD 4, EDS-MD 8 or EDS-MD 16 wired IoT device
gateway by using Telnet or serial ports to configure the device, navigating the Command Line
Interface (CLI), typing keyboard shortcuts, and moving between the levels.
It contains the following sections:
Configuration Using Telnet
Configuration Using Serial Lines
Navigating the CLI Hierarchy
Using Keyboard Shortcuts and CLI
Understanding the CLI Level Hierarchy
Refer to Chapter 5: Commands and Levels for a complete list of levels, commands, and
descriptions.
Configuration Using Telnet
To access and configure the wired IoT device gateway by using a Telnet session over the network,
you must first establish a Telnet connection. You can also establish a Telnet connection by clicking
the Telnet Configuration tab in the Lantronix® DeviceInstaller™ utility. See the DeviceInstaller
Online Help for more information, available on our website www.lantronix.com/support/downloads.
To access the EDS-MD 4/8/16 wired IoT device gateway by using Telnet, perform the following
steps.
1. Click Start > Run. The Run dialog box displays.
2. Type cmd in the dialog box and press OK.
3. Type telnet x.x.x.x (x.x.x.x is the IP address) in a Windows/Linux command prompt.
4. The EDS-MD 4/8/16 wired IoT device gateway is online when the command prompt (>)
displays. You are at the root level of the CLI.
Note: Depending on the level of security, a password may be required.
Configuration Using Serial Lines
Serial Port Command Line Mode
The serial port can be configured to operate in command mode permanently or to be triggered
under specified conditions. See the line <line> Level command description for more
information.
In order to configure and manage the device, connect the computer via a Serial (RS232) cable to
the EDS-MD unit and run a terminal emulation program (e.g., Tera Term). Reference the EDS-MD
Wired IoT Device Gateway User Guide for additional information on connecting the serial port prior
to configuration.

3: Command Line Interface
EDS-MD® Wired IoT Device Gateway Command Reference 11
Boot to CLI and Device Recovery
Serial Recovery mode will temporarily override the line and tunnel settings for the serial line to
allow configuration changes to be made. The line and tunnel settings will be restored once the
user exits the Serial Recovery mode CLI.
To configure the EDS-MD wired IoT device gateway locally using a serial port:
1. Connect a terminal or a PC running a terminal emulation program to one of the wired IoT
device gateway's serial ports.
2. Configure the terminal to the following settings:
9600 baud
8-bit
No parity
1 stop bit
No flow control.
3. Power off the device.
4. Press and hold down the exclamation point (!) key.
5. Power on the device. After about 5 seconds, the exclamation point will display on the terminal
or PC screen.
6. Type xyz within 5 seconds to display the CLI prompt.
Navigating the CLI Hierarchy
The CLI is organized into a hierarchy of levels. Each level has a group of commands for a specific
purpose. For example, to configure a setting for the FTP server, one would navigate to the FTP
level, which is under the configuration level.
To move to a different level—Enter the name of the level from within its parent level. For
example, to enter the tunnel level, type tunnel <number> at the enable prompt. This
displays: <enable> tunnel <number>#.
To exit and return to one level higher—Type exit and press the Enter key. Typing exit at the
login level or the enable level will close the CLI session. If Line - Command Mode is specified
as Always, a new session starts immediately.
To view the current configuration at any level—Type show.
To view the list of commands available at the current level—Type the question mark "?". Items
within < > (e.g. <string>) are required parameters.
To view the available commands and explanations—Type the asterisk (*).
To view the list of commands available for a partial command—Type the partial command
followed by the question mark "?". For example: <tunnel-1>#show? displays a list of all
show commands at the tunnel level.
To view available commands and their explanations for a partial command—Type the partial
command followed by the asterisk (*). For example: <tunnel-1>#show* displays a list of all
show commands and descriptions at the tunnel level.
To view the last 20 commands entered at the CLI—Type show history.

3: Command Line Interface
EDS-MD® Wired IoT Device Gateway Command Reference 12
Using Keyboard Shortcuts and CLI
One useful shortcut built into the EDS-MD 4/8/16 wired IoT device gateway is that the complete
text of a command does not have to be entered to issue a command. Typing just enough
characters to uniquely identify a command, then hitting enter, can be used as a short cut for a
command. For example, at the enable level, "sh" can be used for the "show" command.
Tab Completion is also available using the Tab and Enter keys on the keyboard. Typing the first
few characters of a command, then hitting the Tab key displays the first command that begins with
those characters. Hitting the Tab key again displays the next command that begins with the
original characters typed. You can press Enter to execute the command or you can backspace to
edit any parameters.
The following key combinations are allowed when configuring the wired IoT device gateway using the
CLI:
Table 3-1 Keyboard Shortcuts
Understanding the CLI Level Hierarchy
The CLI hierarchy is a series of levels. Arranging commands in a hierarchy of levels provides a
way to organize and group similar commands, provide different levels of security, and reduce the
complexity and number commands and options presented to a user at one time.
When you start a command line session, you begin at the login level. This level can be password
protected and provides access to high level status, a few diagnostic commands, and the enable
level. Further device information and configuration are accessed via the enable level.
The enable level can also be password protected and is the gateway to full configuration and
management of the wired IoT device gateway. There are commands for gathering and effecting all
elements of device status and configuration, as well as commands that take you to additional
levels. For instance, tunnel specific status and configuration is found under the "tunnel" level, and
network specific status and configuration commands are found under the "configuration" level.
Key Combination Description
Ctrl + a Places cursor at the beginning of a line
Ctrl + b Backspaces one character
Ctrl + d Deletes one character
Ctrl + e Places cursor at the end of the line
Ctrl + f Moves cursor forward one character
Ctrl + k Deletes from the current position to the end of the line
Ctrl + l Redraws the command line
Ctrl + n Displays the next line in the history
Ctrl + p Displays the previous line in the history
Ctrl + u Deletes entire line and places cursor at start of prompt
Ctrl + w Deletes one word back
Ctrl + z Exits the current CLI level
Esc + b Moves cursor back one word
Esc + f Moves cursor forward one word

3: Command Line Interface
EDS-MD® Wired IoT Device Gateway Command Reference 13
An overview of the levels in the EDS-MD 4/8/16 wired IoT device gateway is presented in Figure 3-
2 CLI Level Hierarchy below.
Figure 3-2 CLI Level Hierarchy
Commands at the login level (see Figure 3-3 Login Level Commands below) do not affect current
configuration settings and are not displayed initially. If you type ?, you will see the login sub-
commands. These commands provide diagnostic and status information only.
Figure 3-3 Login Level Commands
>?
clrscrn exit
iperf <params> ping <host>
ping <host> <count> ping <host> <count> <timeout>
show show history
show lines tcpdump <parameters>
trace route <host> trace route <host> <protocol>
enable
>

3: Command Line Interface
EDS-MD® Wired IoT Device Gateway Command Reference 14
Note: To configure the EDS-MD 4/8/16 wired IoT device gateway, you must be in the
enable level and any of its sub-levels. Figure 3-4 below shows the enable level
commands.
Figure 3-4 Enable Level Commands
>enable
(enable)#?
auto show interfaces auto show processes
clrscrn configure
connect connect line <line>
device disable
dns email <number>
exit filesystem
iperf <params> kill ssh <session>
kill telnet <session> line <line>
ping <host> ping <host> <count>
ping <host> <count> <timeout> reload
reload factory defaults show
show history show interfaces
show ip sockets show lines
show processes show sessions
ssh ssh <optClientUsername> <host>
ssh <optClientUsername> <host> <port> ssl
tcpdump <parameters> telnet <host>
telnet <host> <port> trace route <host>
trace route <host> <protocol> tunnel <line>
write xml
(enable)#
See the Chapter 5: Commands and Levels at the end of this document for a complete list of levels,
commands, and descriptions.

EDS-MD® Wired IoT Device Gateway Command Reference 15
4: Configuration Using XML
The EDS-MD wired IoT device gateway provides an Extensible Markup Language (XML) interface
that you can use to configure wired IoT device gateways. Every configuration setting that can be
issued from the Web Manager and CLI can be specified using XML.
The wired IoT device gateway can import and export configuration settings as an XML document
known as an XML Configuration Record (XCR). An XCR can be imported or exported via the CLI,
a Web browser, FTP, or the wired IoT device gateway file system. An XCR can contain many
configuration settings or just a few. For example, it might change all of the configurable
parameters for a wired IoT device gateway, or it may only change the baud rate for a single serial
line. Using XCRs is a straightforward and flexible way to manage the configuration of multiple
wired IoT device gateways.
XML Configuration Record Document Type Definition
An XML document type definition (DTD) is a description of the structure and content of an XML
document. It verifies that a document is valid. XCRs are exported using the DTD as shown in
Figure 4-1 DTD for XCRs.
Figure 4-1 DTD for XCRs
<!DOCTYPE configrecord [
<!ELEMENT configrecord (configgroup+)>
<!ELEMENT configgroup (configitem+,configgroup*)>
<!ELEMENT configitem (value+)>
<!ELEMENT value (#PCDATA)>
<!ATTLIST configrecord version CDATA #IMPLIED>
<!ATTLIST configgroup name CDATA #IMPLIED>
<!ATTLIST configgroup instance CDATA #IMPLIED>
<!ATTLIST configitem name CDATA #IMPLIED>
<!ATTLIST value name CDATA #IMPLIED>
]>
The EDS-MD 4/8/16 wired IoT device gateway DTD rules state the following:
The XML document element is a <configrecord> element. This is the root element.
A <configrecord> must have one or more <configgroup> elements and can have a
version attribute.
A <configgroup> must have one or more <configitem> elements and can have name
and instance attributes.
A <configitem> element must have one or more <value> elements and can have a name
attribute.
A <value> element can have only data and can have a name attribute.
The name attribute identifies a group, item, or value. It is always a quoted string.
The instance attribute identifies the specific option, like the serial port number. The "instance"
attribute is always a quoted string.

4: Configuration Using XML
EDS-MD® Wired IoT Device Gateway Command Reference 16
Note:
The name for each <configgroup> (specified with the name attribute) is the group
name listed in the Web Manager XCR groups or with the "xcr list" CLI command. See
the EDS-MD Wired IoT Device Gateway User Guide for more information about the
XCR groups.
An empty or missing <value> element in each present <configgroup> clears the
setting to its default.
Quick Tour of XML Syntax
Declaration
The first line, <?xml version="1.0" standalone="yes"?>, is called the XML declaration.
It is required and indicates the XML version in use (normally version 1.0). The remainder of the file
consists of nested XML elements, some of which have attributes and content.
Element Start and End Tags
An element typically consists of two tags: start tag and an end tag that surrounds text and other
elements (element content). The start tag consists of a name surrounded by angle brackets, for
example <configrecord>. The end tag consists of the same name surrounded by angle
brackets, but with a forward slash preceding the name, for example </configrecord>. The
element content can also contain other "child" elements.
Element Attributes
The XML element attributes that are name-value pairs included in the start tag after the element
name. The values must always be quoted, using single or double quotes. Each attribute name
should appear only once in an element.
Figure 4-2 shows an XML example which consists of a declaration (first line), nested elements with
attributes and content.
Figure 4-2 XML Example
<?xml version=”1.0” standalone=”yes”?>
<configrecord>
<configgroup name = “serial command mode” instance = “1”>
<configitem name = “mode serial string”>
<value>disable</value>
</configitem>
</configgroup>
</configrecord>
The EDS-MD 4/8/16 wired IoT device gateway uses the attributes in the following subsections to
label the group configuration settings.

4: Configuration Using XML
EDS-MD® Wired IoT Device Gateway Command Reference 17
Record, Group, Item, and Value Tags
A <configgroup> is a logical grouping of configuration parameters and must contain one or
more <configitem> elements. It must have a name attribute and may have an instance
attribute.
A <configitem> is a specific grouping of configuration parameters relevant to its parent group.
An item takes the name attribute and must contain one or more value elements. For example, the
line group might have parameters such as baud rate, data bits, and parity.
A value may specify the value of a configuration parameter. It may contain the name attribute. In
this example, a value of 9600 might be specified for baud rate; 7 may be specified for data bits,
and even may be specified for parity.
A name attribute identifies the group, item, or value. It is always quoted (as are all XML attributes).
For example, a group that contains serial port parameters has the name "line".
An instance attribute identifies which of several instances is being addressed. It is always quoted.
For example, the serial port name (in the line configgroup) has the instance "1" to indicate serial
port 1 or "2" to specify serial port 2.
The following figures show examples of XML configuration records and the use of the
<configrecord>, <configgroup>, <configitem>, and <value> XML elements.
Figure 4-3 XML Example
<?xml version=”1.0” standalone=”yes”?>
<configrecord>
<configgroup name = “serial command mode” instance = “1”>
<configitem name = “mode”>
<value>disable</value>
</configitem>
</configgroup>
</configrecord>
Figure 4-4 XML Example of Multiple Named Values
<?xml version="1.0" standalone="yes"?>
<configgroup name = "ethernet" instance = "eth0">
<configitem name = "speed">
<value>Auto</value>
</configitem>
<configitem name = "duplex">
<value>Auto</value>
</configitem>
</configgroup>

4: Configuration Using XML
EDS-MD® Wired IoT Device Gateway Command Reference 18
Figure 4-5 XML Example of Multiple Items
<configgroup name="ssh server">
<configitem name="host rsa keys">
<value name="public key"/>
<value name="private key"/>
</configitem>
<configitem name="host dsa keys">
<value name="public key"/>
<value name="private key"/>
</configitem>
<configitem name="delete authorized users">
<value>disable</value>
</configitem>
<configitem name="authorized user delete">
<value name="name"/>
</configitem>
<configitem name="authorized user" instance="">
<value name="password"/>
<value name="public rsa key"/>
<value name="public dsa key"/>
</configitem>
</configgroup>
Figure 4-6 XML Example with Multiple Groups
<?xml version="1.0" standalone="yes"?>
<configgroup name = "telnet">
<configitem name = "state">
<value>enable</value>
</configitem>
<configitem name = "authentication">
<value>disable</value>
</configitem>
</configgroup>
<configgroup name = "ssh">
<configitem name = "state">
<value>enable</value>
</configitem>
</configgroup>

4: Configuration Using XML
EDS-MD® Wired IoT Device Gateway Command Reference 19
Importing and Exporting an XML Configuration File
An XCR can be imported or exported using the following methods:
Filesystem-XCRs can be saved to the wired IoT device gateway file system and imported or
accessed as needed. See Best Practices on page 19 or the Filesystem Browser section in the
EDS-MD Wired IoT Device Gateway User Guide.
CLI-XCRs can be imported (captured) or exported (dumped) directly to a Telnet, SSH, or
serial line CLI session. Capturing an XCR can be started by pasting a valid XCR directly into
the CLI prompt. The EDS-MD 4/8/16 wired IoT device gateway immediately processes the
configuration record, changing any settings specified. This can be done on any level, including
the root. Special tags in the XML allow for providing root and enable level passwords so that
this can also be done at the password prompt.
Web browser-Web Manager can be used to import and export an XCR to the wired IoT device
gateway file system. It can also be used to import an XCR from an external source such as
your local hard drive.
FTP-The wired IoT device gateway FTP server can export and import XCRs when an FTP get
or put command on the filename (edsmd.xcr for export, edsmd_import.xcr for import; both are
under the pwxc directory) is requested. On export (FTP get of edsmd.xcr), the FTP server
obtains the current XCR from the EDS-MD 4/8/16 wired IoT device gateway and sends it as a
file. On import (FTP put of edsmd_import.xcr), the FTP server processes the file by sending it
directly to the XML engine. In both cases the wired IoT device gateway filesystem is not
accessed. The files edsmd.xcr and edsmd_import.xcr are not read from or written to the file
system. See FTP in the EDS-MD Wired IoT Device Gateway User Guide.
Best Practices
You can import or export an entire XCR, or just a portion of it, by specifying the group name and/or
group instances. In the examples below, import and export operations are performed from the CLI
on the local filesystem and require a XCR on the local filesystem. The Web Manager provides the
same functionality.
Caution: Using Microsoft Word to edit and save an XCR will change the format of
the file and make it incompatible with the EDS-MD 4/8/16 wired IoT
device gateway. This is true even if the file is saved as Plain Text (.txt) or
an XML Document (.xml). Notepad, a third party text editor, or a
specialized XML editor should be used instead.
Importing
The following syntax can be used to import configurations from a file:
xcr import <file>
xcr import <file> <groups and/or group:instances>
The first line imports all groups specified in the XML config record named in <file>. Any filename is
valid, and the file name and extension are not important.
In the second line:
Instance follows group with a colon (see the third example on the next page).
Multiple groups are separated with a comma.

4: Configuration Using XML
EDS-MD® Wired IoT Device Gateway Command Reference 20
Any white space requires the list of groups to be quoted.
Only the named groups get imported, even if the XCR contains additional XCR groups.
The following syntax can be used to export configurations to a file on the wired IoT device gateway
file system:
xcr export <file>
xcr export <file> <groups and/or group:instances>
The same guidelines above regarding importing configurations also apply to exporting
configurations. If no groups are specified, then the export command will export all configuration
settings to the file. If instances are specified after the groups, only those group instances are
written. If no instance is specified, all instances of that group are written.
Exporting
The following example exports only the accept mode tunneling settings for line 1 to the file
"tunnel_1.xcr" on the wired IoT device gateway filesystem:
xcr export tunnel_1.xcr "tunnel accept:1"
The following example exports only the connect mode tunneling settings for all ports to the file
"tunnel_all.xcr" on the wired IoT device gateway filesystem:
xcr export tunnel_all.xcr "tunnel connect"
The following example imports only the settings for line 2 from an XCR named "factory_config.xcr"
on the wired IoT device gateway filesystem. If "factory_config.xcr" has other configuration settings,
they are ignored:
xcr import factory_config.xcr "line:2"
The following example imports only line settings for all ports from a configuration record on the
wired IoT device gateway filesystem named "foobar.xcr":
xcr import foobar.xcr "line"
To import only disconnect mode tunnel settings for port 1 and all serial line tunnel settings for port
2 from an XML configuration record named "production.xcr" that contains these settings (and
possibly more), issue the following command:
xcr import production.xcr "tunnel disconnect:1"
The following example imports all tunneling settings and line settings for all serial ports from a file
named xcr_file:
xcr import xcr_file "tunnel accept, tunnel connect, tunnel
disconnect, tunnel modem, tunnel packing, tunnel serial, tunnel
start, tunnel stop, line"
The following example exports only accept mode tunneling settings on serial port 1, and line
settings on serial port 2 to a file named tunnel_config_t1_l2.xcr on the wired IoT device gateway
filesystem.
xcr export tunnel_config_t1_l2.xcr "tunnel accept:1, line:2"
The following example exports connect mode tunneling and line settings for all ports to the file
tunnel_config.xcr on the wired IoT device gateway filesystem:
xcr export tunnel_config.xcr "tunnel, line"