Hi,
I am testing the design of new remote site topologies for my organisation;
We are using a Remote AP to tunnel back to us over the internet, which carries vlan 290 on the wired port profile (vlan 290 terminates on our core). Connected to the RAP's wired port is a managed switch with an IP in the vlan 290 address range.
This connectivity is fine.
If I connect a Campus AP to vlan 290 (via the switch or directly to the RAP), then it gets an IP from DHCP, finds the controller successfully with ADP and I can ping the controller address all without issue - yet it fails to bring the CAP online.
If I connect a Campus AP to a different vlan on the switch (local vlan as it is a L3 switch, with a default route pointing to the vlan 290 gateway address on our core), then the CAP works exactly as expected.
Can anyone explain this difference in behaviour?
It appears to be a consistant behaviour with the controller not liking a CAP that is using tunnelled addressing.