NiagaraAX hosts and network communication

In a NiagaraAX installation there is a wide variety of possible communications between NiagaraAX hosts. The following list presents common types of NiagaraAX host network communication and a description of the communication:

The BUI is used to initiate communication from any client host to any NiagaraAX host for the purpose of:

viewing real-time control information

maintaining a station (through the use of servlets)

viewing station data (logs, alarms, schedules, and other information

These are communications that are typically initiated by a Systems Integrator (SI) from an AXSupervisor or remote PC using Workbench or platform tools. The receiving host (or server) could be any NiagaraAX host. The communication could be initiated to perform any of the following tasks:

create a new station

maintain or administer a live station

change host configuration

add users to the host

install a station

install software or licenses

perform database administration

this is communication that is initiated by any NiagaraAX host that is set up to archive logs (histories). These logs are either “pushed” (exported) to or “pulled” (imported) by a remote AXSupervisor for long term storage.

This is communication initiated from any NiagaraAX host that is set up to remotely archive alarms. These alarms may be sent to any AXSupervisor that is set up to archive the alarms. Usually the recipient host runs the Alarm Console for the purpose of acknowledging the alarms.

This is communication initiated from an AXSupervisor to acknowledge an alarm on the NiagaraAX host that is archiving the alarm.

This is communication that may be initiated from any NiagaraAX host to any other NiagaraAX host for the purpose of exchanging real-time data via the Niagara proxy points.

This communication is a timed ping that may be initiated from any NiagaraAX host to the IP address of any other NiagaraAX host for the purpose verifying network connectivity. If the ping fails over a specified time, the initiating host generates a station alarm.

Telnet, FTP, or Hyperterminal communications from Win32-based hosts to QNX-based hosts, as “alternative” means to accomplish host or station maintenance.

Email alarm notification (notifications or acknowledgements) from any NiagaraAX host that is running the email service to any SMTP mail server.

Remote printer alarm notification from any AXSupervisor to a networked printer.

Time synchronization from any NiagaraAX host with the TimeSync service to a time server in order to synchronize the host time. The server could be a NiagaraAX host providing this function or any other server running the Internet Time Protocol.

Station backups using a connection from a NiagaraAX Workbench that has the backup service installed. The target NiagaraAX host (JACE, Supervisor) must have the backup module installed.