Configuring Connect for Ethernet
IT department required
It is advised, that you notify the IT department or person who manages the sites network of the installation of a Connect, to ensure network permissions and access requirements are met in a timely manner and to avoid delays in installation.
Connect can be configured for ethernet via DHCP (with or without a reservation) or static IP.
DHCP
By default, the Connect can be given an I.P. address, dynamically, via a local DHCP Server. This means that when the Connect is plugged into the Ethernet port, there is no further configuration of the Connect required.
DHCP, with a reservation
A DHCP reservation ensures the Connect is consistently given the same IP address by the DHCP server, which may be a requirement if firewall rules are being applied (see below).
This will be managed by the IT department, who will ask for the MAC Address of the Connect, to enable the reservation before installation.
Static IP
Networks lacking a DHCP Server, or restricted in other ways, may require the a 'Static IP Address' which will be supplied by the IT department managing the Network.
Obtain the following IP details from the IT department:- IP address
- Subnet mask
- Gateway IP
- DNS 1
- DNS 2 (Optional)
Once these details have been provided by IT, the Nimbus Support Team can configure the IP details.
WARNING: Connect communication can be interrupted, if any permissions changes to the network are made, after configuration to the device. Please seek assistance from the persons or department responsible for the network, amend any issues that may arise. Network changes without planning can result in an unscheduled callout to site.
Firewalls and Network Restrictions
Many networks have firewalls and other restrictions that may prevent the Connect communicating with Nimbus. We require the following:
- Open Outbound TCP/IP Port 5684, from the Connect to nimbus.lancontrolsystems.com
- No network access control lists being applied to the Network data port being used by the Connect.
Note: If a Connect is NOT communicating (showing offline in Nimbus), usually one, or a combination, of the above requirements may have been missed.