One-Net/DASDEC User Manual
5-106
v3.0 | r1016
Various information fields must be configured to identify and correctly communicate to
the EAS NET remote client. Common to all are:
Client Interface Name
- This text box allows the user to give the client interface a
descriptive name. These names appear in the selection list.
Client Enable/Disable
- This check box enables and disables the EAS NET client.
Remote EAS NET Host IP Address
- Displays the IP address of the remote EAS NET host
where the EAS NET event info is sent.
EAS NET Event Transfer Protocol
- Displays the event transfer protocol (the LAN
communication method used to send the alert event data). Depending on the event
transfer protocol, other configuration fields are necessary or optional. Some protocols
require passwords, others use encryption keys. Most provide for optional data file
connections.
The event transfer protocol options are:
•
Secure Copy (SCP)
– Uses the Secure Shell (SSH) network protocol for both the data
file transfers and event file transfer. No passwords are needed for any of the Secure
Shell protocols (
1.3
). Instead, the EAS device public ssh key id (under /root/.ssh/id_
dsa.pub and also displayed at the bottom of the
System > Status > Network
screen)
must be added into the remote host’s authorized ssh keys list. The keys provide for
encrypted data transfer and for secure authentication without a password.
•
Secure Shell STDIN Only (SSH)
– Uses the Secure Shell (SSH) network protocol for
the event file transfer. No data files can be sent. This protocol requires that the
receiving device read the EAS NET event file from standard input from within the
shell script. In such a configuration, SCP and SSH login to the EAS NET user will not
present to the remote platform shell.
•
Secure Shell STDIN & Copy (SSH with SCP)
– This is a variation on protocol #2
above. The event file is sent as in #2, but the Web interface will display a field to
enter a second user account for sending data files to the remote host. The Secure
Shell (SSH) network protocol is used for both transfers.
•
File Transfer Protocol (FTP)
– Uses the File Transfer Protocol (FTP) network protocol
for both the data file transfers and event file transfer. A password is required. FTP
does not encrypt or secure passwords during transmission. The password is sent
in clear text to the remote host FTP daemon. If security is an issue, do not use or
design an FTP based EAS NET scheme. Some FTP daemons refuse passive port
connections. Use the provided checkbox to enable a non-passive connection if
needed.
•
TCP event notification
– Uses a TCP socket from the EAS device to the remote host
to send the alert event file. For sending the optional data files, one of FTP or SSH
SCP network protocols can be selected. A valid user account on the remote host
must be entered. The information described above for passwords and keys apply,
depending upon the chosen data protocol.
•
DVS168/EARS
– This is a special case of EAS NET. A TCP socket is used to
communicate an event notification, while FTP is used to send data files.
•
Legacy Mediaroom
– This is a special protocol bundled under EAS NET when the
Microsoft© Mediaroom
TM
option is licensed.
•
Mediaroom2
– This is a special protocol bundled under EAS NET when the
Microsoft© Mediaroom
TM
option is licensed. This is in accordance with the
Mediaroom 2.0 software.
•
MINERVA
– This is a special protocol bundled under EAS NET when the Minerva
Note
T
he
EAS_NET Event
Transfer Protocol
pull-down menu selection
will dictate the available
configuration settings
within this screen. The
following configuration
setting descriptions
represent the most
commonly used. Not
all settings will be
available for the selected
EAS_NET Event Transfer
Protocol. See
Other
possible EAS NET Client
Configurations Options
(below).
