07-26-2012 02:03 PM
I have 2 AP's at a remote branch that I need to provision on a 3400 controller at the main site. The 2 locations are connected via a point-to-point circuit. Default route for all traffic at the remote branch is down the p2p to the main site. The 2 AP's are unable to reach the controller, even with manually putting in the controller IP address into each AP. Here are more detail sinto the IP addressing:
controller is trunked to the core switch on native vlan 1 (10.9.1.0/24) )with an address of: 10.9.1.200 and default gateway of 10.9.1.1
vlan 6 (main site access points) L3 interface and vlan defined on core switch (10.9.6.0/24). Vlan 6 is also defined on the controller (10.9.6.15/24)
P2P router to remote branch address: 10.9.240.1
vlan 1 on core switch (10.9.5.0/24, L3 = 10.9.5.1)
vlan 106 (access points)=10.9.106.0/24
P2P router to main site: 10.9.240.2
Default route for entire site: 0.0.0.0 /32 10.9.240.1
Can AP's register on controllers on dissimmilar networks?
07-27-2012 05:17 AM
Normally you would want to provision the AP's just like a local client using either DHCP or static IP's. They would be on the same subnet as local users and use an IP and default gateway just as the local clients. Then be sure to open up the required ports from the AP's to the controllers if you have any ACL's or firewalls between them.
Then separately you could provision different subnets for the different ssid's to separate your wifi users from your wired users.
Hope that helps,
07-27-2012 07:03 AM
Thanks Ian. Unfortunately (or fortunately) our standards already include everything you described. The question still remains...is it possible for AP's to be provisioned on a controller that resides on a dissimilar network?