Edge FAQ

How are commands set to devices?

When a user initiates a command via the Xyte UI, API or other methods, the command is queued in the Xyte cloud until the next time the Edge initiates a synchronization process. During this process the Edge gets list of all commands to execute (either commands to run on the device, claim new devices or commands to perform on the Edge itself).

What is the period of data collection?

Each device family has a different driver built by the Xyte team. Depending on the monitor Device's capabilities and protocol, the collection period is defined not to overwhelm the device with data collection requests and can be between 30 seconds and up to 5 minutes.

What happens if my device is assigned a new IP address?

Xyte identifies and communicates with devices using their IP address. If a device is assigned a new IP address — for example after a reboot, a DHCP lease renewal, or a network change — Xyte has no way to automatically detect that the IP has changed. As a result, the device will appear as Device offline and will remain in that state until the correct IP is updated manually.

To prevent this from happening, we recommend one of the following:

• Static IP address — assign a fixed IP directly on the device so it never changes.

• DHCP address reservation — configure your DHCP server to always assign the same IP to the device based on its MAC address.

• Hostname resolution (DNS) — use a hostname instead of an IP address where supported.

  Use a name the Edge host itself can resolve. Check it with nslookup <name> on the Edge host. If that returns an address, the Edge can use the name. If the device's ping test returns Cannot send ICMP ping packets, the name most likely didn't resolve.

If a device is already offline due to an IP change, or you are re-addressing a whole subnet: open the device in Xyte, click the pencil next to Device IP / Hostname, enter the new address and save. Use Test connection in that dialog to confirm the Edge reaches the device at its new address. The Edge itself needs no change in Xyte when its own address moves, as long as it still reaches the internet and the devices' subnet.

On plans that include API access, the same change can be scripted for many devices at once with the Organization API's Update Hostname endpoint, either directly or through the Xyte CLI, which wraps that API.

What is the maximum delay for device claiming and heartbeat on the Edge?

Up to 1.3 seconds for claiming and 3 seconds for heartbeat (HB).