Link to home
Start Free TrialLog in
Avatar of eagle3344
eagle3344

asked on

Cisco AP's using Cisco Wireless controller on another subnet?

I am currently using about 10 WL AP's (Cisco AIR-CAP2602e) on the same subnet as my Cisco 2500 Wireless Controller. I need to put in 2 more AP's at a separate building with a different subnet.

 I "primed" the AP per Cisco's instructions by putting a static IP address on the 2 new AP's and putting in the IP address of the WL controller. Once plugged in at the new building I could seem them within the controller, but when I connected my laptop to the new AP's they gave me an IP address from the main location, not the new subnet.

Can someone tell me what setting I need to change to make this work?

Thank you.
ASKER CERTIFIED SOLUTION
Avatar of Craig Beck
Craig Beck
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of eagle3344
eagle3344

ASKER

craigbeck,

I just printed off that guide...much appreciated!

So I am planning on only using this wireless for 2 tablets using a citrix application at the main location. Are you saying that the AP handles all of the routing for clients connected to it? In other words, once a client gets an IP address from the main location and the client then needs to either get internet access or get to the citrix server the AP will handle that routing??? If that is the case, then I should be able to use it as is since I will only need citrix and internet for these tablets. When I was testing onsite I was hardwired in and saw that I got two different IP addresses I stopped at that point and didn't unhook from the hardwire and test.

As you can probably tell wide area is not my area of expertise, but was just thrust into figuring it out so I appreciate your help.
In AP local mode all client traffic goes back to WLC.

In AP FlexConnect mode the traffic drops straight onto the switch where the AP connects (so follows the same routing as a wired client).

Given your requirements I'd just leave everything as it I now.
I tested this in local mode and it worked with no issues. Since the application I am trying to get to is at our main facility anyway this really seems to have worked out just fine.

I appreciate your assistance...thanks for your time!
My pleasure :-)