Lantronix EDS4100 EDS - Command Reference - Page 18

4: Configuration Using XML the CLI prompt. Evolution OS 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 device server file system. It can also be used to import an XCR from an external source such as your local hard drive.  FTP-The device server FTP server can export and import XCRs when an FTP get or put command on the filename eds[4100,8pr,16pr,32pr].xcr is requested. On export (FTP get of eds[4100,8pr,16pr,32pr].xcr), the FTP server obtains the current XCR from Evolution OS™ and sends it as a file. On import (FTP put of eds[4100,8pr,16pr,32pr].xcr), the FTP server processes the file by sending it directly to the XML engine. In both cases the device server filesystem is not accessed. The file eds[4100,8pr,16pr,32pr].xcr is not read from or written to the file system. See FTP in the EDS User Guide.  TFTP-TFTP supports XCR importing. Due to limited security capabilities of TFTP, the option is disabled by default. 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 Evolution OS. 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 xcr import The first line imports all groups specified in the XML config record named in . Any filename is valid, and the file name and extension are not important. Caution: The filename eds[4100,8pr,16pr,32pr].xcr is not acceptable, because performing a FTP get on that name produces the current configuration and does not perform an FTP from the filesystem. Also, the filename eds[4100,8pr,16pr,32pr].xsr is not acceptable, because performing an FTP get on that name produces the current status and does not get anything from the filesystem. 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.  Any white space requires the list of groups to be quoted. EDS Command Reference 18