Digital Alert Systems DASDEC-II MANUAL - Manual (Page 97)

Digital Alert Systems: DASDEC User Manual
91
encryption keys. Most also provide for optional data file connections.
The event transfer protocol options are:
1. 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 all of the Secure Shell protocols (1.3), passwords are
not used. Instead, the DASDEC II public ssh key id (under /root/.ssh/id_dsa.pub and also displayed at the
bottom of the Server > Status > Network page) 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.
2. 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.
3. 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.
4. 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 demon. 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.
5. TCP event notification – Uses a TCP socket from the DASDEC II 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.
6. 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.
7. Legacy
Mediaroom – This is a special protocol bundled under EAS NET when the Microsoft©
Mediaroom TM option is licensed.
8. 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.
9. MINERVA
– This is a special protocol bundled under EAS NET when the Minerva option is licensed. A
TCP socket is used to communicate an EAS event notification as per the Minerva protocol.
10. WideOrbit – This is a special protocol bundled under EAS NET when the EAS NET Automation option is
licensed.
11. RCS Nexgen – This is a special protocol bundled under EAS NET when the EAS NET Automation option
is licensed.
Remote EAS NET Host Port - The field displays the port on the remote EAS NET host where the EAS
NET event info is sent.
EAS NET User - Displays the user account name on the remote device. Files sent to the remote host
will by default be copied relative to this account home directory.
Current Schema
The schema determines key names of the information fields sent to the EAS NET client's remote host. It
also determines file names and paths for any files sent to the remote host. The schema can be edited
by clicking on the Edit/Review Schema button.