Ensuring that traffic to/from APs arrives on the same controller port

My good friend Leigh is really doing a bang up job on his blog...  Putting me to shame!  It's given me motivation to make the following post though.

Here's something that I just read in the WLC Configuration Best Practices:

"With the Cisco IOS Software Release 12.2(33)SXH6, there is an option for PFC3C mode chassis to exclude VLAN in the Load-distribution . Use the port-channel load-balance src-dst-ip exclude vlan command in order to implement this feature. This feature ensures that traffic that belongs to a LAP that enters on the same port."

The bold is original, I added the italics for emphasis.  On my configs I've always used port-channel load-balance src-dst-ip, but never exclude vlan...  Seems like a good thing to try my next go-round.

2710 is now working with WCS!!!

So, here's the deal.

The Location Appliance is finally working with WCS. What did I do to get it working? I followed a suggestion at this site:

http://supportwiki.cisco.com/ViewWiki/index.php/Unable_to_add_a_Wireless_Location_Appliance(WLA)_to_a_Wireless_Control_system(WCS)

Namely, step 4. I guess I had been assuming this whole time that I had changed the HTTPS username/pass... Nope. It was default. D'oh! I still had to check the HTTPS box though, since the 2710 still isn't responding to HTTP. Now, to get it synchronized with the WLCs!

2710 Location Appliance

For the past couple of days, I've been working on configuring a 2710 Location Appliance. Our division got it used from another division, so I had to start by resetting the root password. I've attempted reconfiguration manually, and when that failed, I've run the automatic setup script. I've also updated the code to 6.0 (I know; it's not the version that is going to be on the CCIE lab, but it's the version of code that we're running on our network here).

It's been a good refresher of using Linux and VI to edit the setup and find files. I'm still not 100% complete, but feel I'm making good progress. The 2710 is back online from its most recent reboot, so back to work!

I posted this on my personal blog by mistake, so now it's in 2 places...