thanks for your response. How can this be done? In my environment both Wireless-802.1x-NACs are in Engine group A. (f.e. 192.168.4.216 and 192.168.64.216)
Guest NAC is in engine group B. (f.e. 192.168.64.204)
Both ECAs are added as switches to both NACs in Engine Group A with both NACs configured as primary and secondary engine.
As soon as I add an ECA as switch in Engine Group B by configuring it as primary or secondary engine there, this ECA disappears from the remaining former NAC.
In the following screenshot I want to add ECA 192.168.64.201 to guest NAC 192.168.64.204. NAC Manager Java Client asks about this, because this ECA is already added to NACs 192.168.4.216 and 192.168.64.216:
XMC WebClient does not ask and simply moves switch to the other appliance. The switch only appears in those appliance groups with NACs which are configured as primary or secondary engine of the switch. Is there a workaround?
You don’t need to add a third NAC engine for this. Seems like overkill unless you are planning a massive deployment of clients.
Our NACs have only IP interfaces in our management IP space. A NAC which delivers portal to guest users must be reachable for those guest users (I think) to be able to see guest portal login page. So I assume I have to activate second interface on Guest Portal NAC and use an IP adresss which is reachable from guest users IP space. We wanted to avoid this on our Main-Wireless-NACs or ECA. For this reason we considered a dedicated NAC for Guest Portal.