AP310 won't adopt to VC

[JohanHendrikx]

At a remote site I have 9 new AP310.

2 Ap's won't connect to the VC.

AP have an IP-address  and the DHCP server send option191.
AP cann't communicate with the gateway so no RF-manager can be found. Cann't ping the default gateway. Other devices (L2)  can be reached

In the logging of the AP I see:

Jan 01 01:47:47 2022: %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING: Conflicting snoop entry found :Ethernet Src Mac: 00-04-96-A0-7C-1D, Ethernet Dst Mac: 00-DC-B2-3A-9B-EF, ARP Src Mac: 00-00-5E-00-01-01, ARP Dst Mac: 00-DC-B2-3A-9B-EF, ARP Src IP: 10.2.116.254, ARP Target IP: 10.2.116.1, Snoop Table MAC = 00-04-96-A0-7C-1D, Snoop Table IP = 10.2.116.254
Jan 01 01:47:47 2022: %KERN-4-WARNING: [ 1630.319376]

10.2.116.254 is the L3 router of that netwerk and is a VRRP configuration.

How can I solve this?

[JohanHendrikx]

Christoph,

The controller is locate at HQ. At the remote site there are AP310. The AP310 isn't a virtual controller.

[Christoph_S]

Hello Johan,

Are we talking about remote adoption by a VX9000 controller or by an AP310 virtual controller? If it's the latter, this is not supported as those are intended for adoption in same broadcast domain over L2. 

Please advise. 

Thank you,