We've been noticing lateley that the forwarding state on the internal and external radios is 'Blocking' on some access points and 'Forwarding' on others. All of the access points are basically configured the same with the same code (12.03T) on them (although this behavior has been seen on earlier releases).
The access points appear to put themselves in this blocking state and can not be easily forced into forwarding again. This unexpected change of state bounces users from one access point to another and can terminate their VPN sessions in the process (even if both access points are of the same VLAN).
The whole thing reminds me of spanning tree, but STP doesn't appear to be mentioned in any of the configuration pages for the radios.
I don't think the forwarding state has anything to do with it.....When the forwarding state reads blocking it means this is the state when no stations are associated. When you see forwarding you have stations associated. I would check the channel distribution of your APs, and make sure that you have your channels spread out. Also there are some issues with VPN connections and roaming on APs.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...
I have created a Powershell script to automatically add a Wireless Guest
User on Cisco WLCs. (tested on 2500 Series) The script should be
completely self explanatory. Prerequisites: Powershell SNMP Module
(Install-Module -Name SNMP) SNMP Write Access to y...