Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 874
  • Last Modified:

New Cisco Wireless Configuration

we have just purchased a Cisco aeronet hardware setup for our multiple offices, to replace a very shaky Sonicpoint configuration (2 years with open support tickets with Sonicwall for dropping connections, and still no solutions!).

The plan is to set up across our 3 sites, with 2 3501 APs in our London and Manchester offices, and 1 3501 in our smaller Liverpool office; with the central 2504 controller in our Manchester office.  We currently use separate private and public SSIDs at each site, but i am planning to make this just a single SSID for public, and another for Private network.  From my understanding, I will need to configure the remote APs for H-REAP and also will need to setup VLANs for this all to work properly.  

The previous configuration was a lot simpler, due to the Sonicwall NSA4500 firewalls at each site managing the VLANning and general running of the APs at each site!  We are also running true-IP Mitel phones at each site, running through HP Procurve 5400 series PoE switches - very simple configuration, VLAN 1 for data (untagged), VLAN 2 for voice (tagged).

After reading through the multiple documents on Cisco's website I am (as usual with Cisco) a little bogged down in how best to set this configuration up!  There are mentions of using just 1 port on the 2504 for management and trunking to the switch, and others mention using a spearate port for the data trunk.  I am also unclear about how to route the public SSID out through each of the NSA4500 firewalls at each site locally.  

Can anyone offer some advice please?
0
Amaze_IT
Asked:
Amaze_IT
1 Solution
 
Craig BeckCommented:
Firstly, you don't absolutely HAVE TO use H-REAP.  If you have good WAN links and latency is <300ms you can do this without using H-REAP.  The only problem here is that if the WAN link fails between the AP and the controller, your WLAN is DOWN at that site.  If this is acceptable, I'd do it this way.

However, if you need the WLAN to function when the WAN link goes down (or the controller fails) you need to use H-REAP and implement VLANs at your offices.  Choose a different VLAN ID for each office to keep things separate, and create H-REAP AP groups on the controller.

The Cisco H-REAP guide is pretty straight forward from the controller side of things, it's just understanding the switching modes that throws people.  Basically you'll be using a local-local method if you want to use H-REAP, so think of it as a normal trunk port at the switch level.

I'd use one port for the controller - implementing separate ports is confusing and unnecessary for your implementation.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

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