32
Equinox ESP-2 OPTO Serial Hub Installation and User Guide
Section 6 - Configuration Files
The ESP-2 serial hub will accept a DOS or UNIX style text file containing
configuration commands. A configuration file may be loaded from a BootP or DHCP
server for initial configuration. A configuration file may also be downloaded using
the web interface or the configuration utility.
A file-based reconfiguration of an ESP-2 hub may also be initiated using a third party
SNMP agent. An SNMP MIB is available through Equinox Technical Support.
The configuration file is processed one line at a time. If an error is encountered, the
line containing the error and all remaining lines in the file will be ignored. Commands
in lines that were parsed before the errored line will be executed.
6.1 Sample Configuration File
A sample configuration file is available through the ESP-2 web interface. This file
contains every supported command with most of the required and optional parameters
for one serial port. All lines are preceded by a comment character (#).
To use the sample configuration file as a template:
1. Select
Documentation
from the Main Menu.
2. On the ESP-2 Available Documentation page, enable the
Sample Configuration
File
radio button, then click
Apply
. The sample file will be displayed.
3. Copy the file sample file. You may either select and paste the content or save the
frame to your system.
4. Using an editor of your choice, remove the comment character (#) from the
beginning of each line containing a command you wish to execute.
5. Following the rules listed in
File Format and Command Syntax
, tailor the
required and optional parameters to meet your requirements. For example, if the
sample command enables a feature and you wish to disable it, replace the word
enable
with
disable
. Replace address and port parameters with values that are
meaningful to your configuration.
6. Copy and edit the commands as needed to configure both serial ports.
7. Save the customized file.
6.2 File Format and Command Syntax
Configuration files must conform to the following conventions:
•
Each command must begin on a new line.
•
Command words are not case sensitive.
•
Parameters are separated by one or more spaces.
•
Parameters with values that enable or disable connection methods or features use
a space between the keyword and the value. For example:
port 2 tcpserver enable monitordcd enable
ipviadhcp disable
