- Access Points
- Limit: 10 APs per site (WBE758 and WBE718).
- Discovery: APs need to be physically connected to the network - same as switches, in the same broadcast domain as Engage.
- Onboarding: APs need to be in factory-default state, and not managed by Insight.
- If the AP is managed by Insight, Engage will refuse the onboarding. You need to go to Insight and ”remove” the AP from Insight first.
- If the AP isn’t managed by Insight, but previously managed via local GUI with some config on it (user password etc.), Engage will refuse the onboarding. You need to factory-default the AP first.
- Limit: 1 router per site (PR460X).
- Discovery: the router needs to be physically connected to the network on one of its LAN ports - same as switches, in the same broadcast domain as Engage.
- Onboarding: the router doesn’t need to be in factory-default state, it can be previously configured – but it cannot be managed by Insight.
- If the router is managed by Insight, Engage will refuse the onboarding. You need to go to Insight and ”remove” the router from Insight first.
- If the router isn’t managed by Insight, but previously managed via local GUI with config on it (user password etc.), Engage will onboard it nicely.
- During the onboarding, Engage is detecting which LAN port on the router is connected to the AV network.
- Engage asks you to confirm that this is the correct LAN port.
- Router: onboarding is fast, similar to switches.
- APs: onboarding takes a little longer – when firmware upgrade happens during onboarding, it can take up to 15/20 minutes.
- APs: it’s mainly read-only, as most features are managed from Engage, they are greyed out in the local GUI.
- Router: the opposite, you can manage the router using its GUI the way you want (like with switches, it's better not to conflict with Engage, though).
Last Updated:07/07/2025
|
Article ID: 000066442