AvL Technologies AAQ CIP, Setup & Operation Manual

Page: 37 / 41

AAQ Controller Interface Panel (CIP)
36
Label Description
DHCP Client Enabled: Choice to enable the router to be a DHCP client. This is a
choice between automatic and static.
Controller IPv4 Address: The address devices on the WAN will use to communicate to
the router, or if NAT rules are enabled the address devices
on the WAN will use to communicate to the controller.
Controller Subnet: Subnet mask the router will use.
Gateway: The address the router will use to interface outside of the
WAN network.
Secondary Gateway: The address the router will use to interface outside of the
WAN network in case the primary Gateway fails.
DNS: The address of the DNS server on the WAN network.
Remote Power IPv4
Address: The address devices on the WAN will use to communicate to
the remote power cycle device in the CIP.
Remote Power Subnet: Subnet mask the remote power cycle device in the CIP will use.
5.5.3.
Network Example
Below is an example of a CIP setup showing a network diagram of the sample network, how the AAQ controller and
CIP fit into the network scheme, also how to use the tool to configure for the network.
AAQ Controller
CIP
IP: 192.168.129.51
SN: 255.255.255.0 IP: 192.168.129.1
SN: 255.255.255.0
IP: 10.0.0.101
SN: 255.255.248.0
IP: 10.0.0.102
SN: 255.255.248.0
Router
Remote Power Cycle
LAN WAN
IP: 192.168.129.200
SN: 255.255.255.0
Customer PC #1
IP: 10.0.0.1
SN: 255.255.248.0
Customer Server
Internet
IP: 10.0.0.2
SN: 255.255.248.0
Customer PC #2
Figure 59 - Network Example
In this example the CIP is a DHCP server and is able to distribute DHCP addresses to any device on the LAN. Customer
PC #1 has been given the IP Address of 192.168.129.200 from the CIP. It can now communicate to the AAQ controller
using the default 192.168.129.51 address. The internet is reachable by PC #1 by using the CIP router as a gateway,
which in turn the CIP router will pass through the Customer Server and on to the internet.
Since in this case NAT rules are enabled Customer PC #2 can also communicate and control the antenna from the
WAN network. It would communicate to the AAQ controller using the 10.0.0.101 address given to the CIP. In this
case the WAN network could be expansive and PC #2 could be offsite or at a long distance away from the system, but
still able to command and control.