Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 239
  • Last Modified:

Cisco Wireless Controller 2100

I recently got a new Cisco 2100 series wireless controller.
I need to set it up in a multi vlan environment.
Having it connecting and registering WAP that are connected to my switches is not a big issue.
What i'm having trouble figuring out is how to set it up so that i can make use of its 2 POE ports.

What i'm trying to figure out is what VLAN those ports will be in when i connect the WAP to it.
I can set VLAN tags to ports but only if i create new interfaces, and i dont think i would have to create a new interface for each WAP i need to connect.

I hope i'm making myself clear on this if not please ask and i will try to clarify.
1 Solution
I am not a WLC expert but I do own one. The VLANs are not defined on the physical interface like you would with a router or switch, they are defined on your WIFI interfaces that you create within the WLC (I think they call them interfaces but maybe AP groups or something. I dont have it in front of me right now). You can bind a physical interface and VLAN to the WIFI interface after you have created it. When I get to work I can give more info and a screen shot.
curwengroupAuthor Commented:
I dont think i was clear enough.

lets say that in my environment i have 2 vlans 10 and 100
On my switch port i can configure it as a trunk and allow vlans 10 and 100
on the wireless controller i create 2 interfaces 10 and 100
interface 10 is connected to port 1, with ip address and assigned to vlan 10, i can then configure an SSID to that interface
interface 100 is connected to port 1, with ip address and assigned to vlan 100, i can then configure an SSID to that interface
This puts port 1 on the controller in trunk mode and allows communications with the rest of the network.
On a switch i can configure the WAP ports to either vlan so they get an ip address from dhcp and bind to the controller.
However i want to use POE for 2 of my access point, and unfortunately i dont have POE switches.
SO i want to make use of the 2 POE ports on the wireless controller, so i plug a WAP in port 7.
Which VLAN is the device in?
I dont think it matters. The AP doesnt need to be in a VLAN, only the SSID does. Just assign an IP to the WLC interface and assign a compatible IP to the AP. I think that will work. Your AP should show up in the WLC after that. You may have to do some tagging to get your wifi traffic to flow.
Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

curwengroupAuthor Commented:
That seems some how counter intuitive, having to setup an interface on the WLC for each port i want to use with a WAP.
That would mean if i want to hook up 6 WAP i need to setup 6 additional interfaces and use 6 IP's for each of those interfaces either in the same subnet or having to deploy 6 additional subnets.
Yes, I believe that is correct.
The AP will be in the network that is created without a VLAN (untagged).

i.e. you have 3 interfaces in your WLC

1 - mgmnt: vlan identifier 0, Port Number 7
2 - VL10: vlan identifier 10, Port Number 7
3 - VL100: vlan identifier 100, Port Number 7

If you now connect the AP to Port 7, by default it will be on the native vlan and in this configuration the AP and WLC act like a switch trunk.
Istvan KalmarSenior Network EngineerCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now