When a network client connects to the access point or the wired devices, it takes some time before this client appears in Nebula Control Center's client pages, but why is that?
Being a cloud solution, Nebula requires the supported devices to sync the data information to its servers, and in order to avoid high bandwidth utilization of your network or the increase of the device's CPU usage due to permanent connections; the Nebula solution implements a polling interval time to get the device data information. This varies in each product type as the following details:
Being a cloud solution, Nebula requires the supported devices to sync the data information to its servers, and in order to avoid high bandwidth utilization of your network or the increase of the device's CPU usage due to permanent connections; the Nebula solution implements a polling interval time to get the device data information. This varies in each product type as the following details:
- Gateways need 3 minutes to sync and update to the Nebula control center.
- Switches need 5 minutes to sync and update to the Nebula control center.
- Access points need 3 minutes to sync and update to the Nebula control center.
Please note that the first time the device is connected to Nebula, the data polling might take longer as the device is also being configured with your NCC site settings. NebulaFlex™ and NebulaFlex™ Pro supported devices will require a longer time since the devices are also getting converted from another mode to Cloud mode, experiencing reboots within the process.
Comments
0 comments
Please sign in to leave a comment.