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

Cisco Wireless Access Controller 2504 Port Usage

I'm the proud setup person of a new Cisco Wireless Access Controller 2504. I was able to get it setup in a crude fashion for testing, but now want to set it up correctly.

My two wish list items for this deployment are:

1) There will be one controller managing multiple locations with AP's so I wanted to take advantage of H-Reap.
2) I wanted to have a public and a private SSID. The public SSID will tunnel directly out through out ASA. The private SSID will be allowed all access.

So, I'm wondering what is one to do with the four ports specifically?

I'm thinking:

1) Management
2) Trunk for AP's - I guess each office location with AP's will be on their own VLAN and network range?
3) Trunk to Cisco ASA wireless traffic. Each SSID will be on its own VLAN to the ASA.
4) Not sure.
First Last
First Last
  • 2
2 Solutions
I normally put the management on 1.. ports 3-4 for that model are POE. You should have 2 as a trunk port to a switch. I believe you can setup ACL to route a certain SSID (on it's own vlan) to route out the ASA. you wouldn't need another ethernet cord for port 3.

If you setup the 2nd port for trunk and allowed vlan's through you can get all the AP's even if they are on a different switch. Once again, this all depends on your setup and what your trying to accomplish.
"2) Trunk for AP's - I guess each office location with AP's will be on their own VLAN and network range?"
If you create a vlan for each building you will need to setup it's own subnet. Most companies i have worked for have a private SSID and a public SSID. They would be on seperate vlan/subnet.

You stated that the WLC was going to manage multiple locations, max AP's managed by the WLC is 50. Once again, it depends on your demands.
You only need to run port 1 to the switch. Everything will run over that link.
First LastAuthor Commented:
Thank you.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

We Need Your Input!

WatchGuard is currently running a beta program for our new macOS Host Sensor for our Threat Detection and Response service. We're looking for more macOS users to help provide insight and feedback to help us make the product even better. Please sign up for our beta program today!

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