Skip to main content


Why does my device show a blank display or seems not to boot?

Make sure you have a PoE-enabled switch. Even PoE-enabled switches will often only include a combination of some ports for PoE, and other ports not.

Ensure your device connects to a PoE-enabled port. Ensure the cable connects fully to the port. You will generally hear the ANetD jingle within a few seconds of applying power (i.e. connecting the CAT5 cable, or applying power to your switch or injector). If you do not hear this sound, the device most likely is not getting any power. Check into your cable, and switch/router. On switches that support it, make sure to enable LLDP, which will allow the connected devices to negotiate for PoE or PoE+ power.

Some Cisco switches can benefit by configuring the power management on the port to “2x-mode” to handle the inrush current. Set this mode on each switch interface using the command “power inline port 2x-mode”. Also, try a different known-working PoE port (PoE ports often go bad over time on some vendors’ equipment).

Why does my device reset periodically or continually after boot (playing the boot-up sound often)?

In most cases, this results from a possible bad switch port (an occasional reality), or an overloaded switch (even though a given switch might have 4 PoE ports, not all 4 can provide full power consistently in many brands). Try a different PoE-enabled port or a different switch. Lower port numbers generally work better. Higher port numbers provide less power in some brands, if other PoE devices draw power from the lower ports. Choose a reputable switch, and understand its power delivery capabilities. We designed our units to have available the full PoE or PoE+ power per the respective IEEE standard.
Another possible cause results from a unit configured to register to a particular server, but it cannot connect to that server. Check that the server is running and accessible from the subnet on which the unit resides. Access the unit’s Device Status web page, and verify the unit is successfully registering to the server. If the registration is failing, check the cause reported on the status page, as well as the end of the Device Status –> Non-Volatile Log for details on failure causes.

Another possible reason for the rebooting unit comes from an incorrectly specified firmware filename in the configuration file. An incorrect filename or inaccessible file on the server that hosts the configuration file would cause the unit to lock into a constant reboot cycle. The cycle will continue until it finds a correct filename, until you remove the reference from the configuration file. Check the spelling of the filename, and make sure it resides in the same directory as the configuration file.

Why does the boot process seem stalled before completing?

The boot process takes about 20 seconds under normal conditions. See the Install Questions FAQ for the full sequence.
The two common ways the device may appear stalled during bootup: Stalling at “Network Init/DHCP”: If it takes a long time at the “Network Init” stage, then the network may have a connection problem. Either the device cannot get an IP address, DHCP is malfunctioning, or you may have a bad network cable or switch.

Stalling at “Looking for Config”: In some cases, a bootup may take over five minutes, especially after a power disruption during a a previous bootup sequence, or during the first power-up when receiving the unit from the factory – both considered normal behavior situations. However, this behavior should not occur regularly.

Not Finding an Answer?

Please contact our support team with your question.