NiagaraAX network examples

There are many different ways to design and configure NiagaraAX networks. It is possible for each individual networking environment to combine with the project requirements to present a unique challenge for maximizing network efficiency. In addition to understanding general networking principles, it is important to understand NiagaraAX networking.

Please note the following general information points about connecting NiagaraAX devices to a LAN or WAN:

Connection between NiagaraAX hosts on a LAN/WAN will be faster and more reliable than connection via modem (either direct dial or through an ISP).

Niagara proxy points are designed to be used across connections that are always available. The design assumes that connections between linked hosts go up or down infrequently. Therefore, proxy points should only be used on a LAN or WAN, and only on a LAN/WAN that provides reliable connection between hosts.

Access to hosts with private IP addresses can be made from hosts on the same LAN/WAN. Any host (NiagaraAX or other) that needs to be accessed directly from the Internet must have a public IP address. External hosts can only access privately-addressed internal hosts through a virtual private network (VPN).

When connecting to NiagaraAX hosts behind a firewall, certain ports need to be opened on the firewall for access by a BUI client or by an engineering station running Workbench or the platform tools. For more information on ports in the NiagaraAX environment, see About NiagaraAX ports.

The key to success in many installations is early involvement by the IT department at the site. If you are going to connect devices to their LAN/WAN you need to check with them before implementing to learn about their policies so you can follow them.

The following examples represent some of the major characteristics of typical NiagaraAX system architectures and provide some common practices for engineering NiagaraAX environments in both single-site and multiple-site applications.