Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Chapter 10 - Using FTP
SNMP Access Gateway User’s Manual - v1.0 -- 11/99 - Page 40
Chapter 10 - Using FTP
The SNMP Access Gateway contains an FTP server which may be used with TCP/IP FTP client software. The FTP
server may be used to retrieve or delete the events log file, load or retrieve the alarms configuration file, load a
settings file, and load new application software into the SNMP Access Gateway.
The FTP server requires the use of a User ID and password to log into the server. The User ID is collected but not
presently used. The password must match the FTP server password, which may be changed using the SETUP
command menus.
The FTP server supports the DIR command, which indicates the events log file exists and the number of records in
the events log file. The FTP Get and Delete commands may be used with the events log file, using the filename of
EVENTS. Thus, GET EVENTS will retrieve the current contents of the events log file.
The alarms configuration file does not show up in the directory listing via the FTP server. However, the alarms
configuration file may be loaded into the SNMP Access Gateway and retrieved from the SNMP Access Gateway
using the filename of ‘ALMFILE’.
A settings file contains pseudo-SNMP set instructions and may also contain the contents of an alarm configuration
file. A settings file may be loaded into the SNMP Access Gateway using the filename of ‘SETTINGS’.
A new software application may be loaded into the SNMP Access Gateway by loading a file named ‘NEWAPP’ into
the SNMP Access Gateway. Only an application program file made available by RFL should ever be loaded into the
SNMP Access Gateway as an application file. Other files will not properly execute, and will thus result in the
SNMP Access Gateway simply entering load mode, awaiting the loading of a valid application.