On ap1242, if i configure mobility network-id on the SSID manager, I cannont anymore associate with clients.
On 1231, with the same configuration, all works fine.
Anyone had similar issue ? I tryed ( on 1242 ) to add and remove the "mobility network-id ..." several times, and I've seen that clients can associate only without that command. Have someone some documents that explain that behaviour ? is this a bug ?
Connectivity problems in a WLAN network can occur if you use the mobility network-id command incorrectly. You use the mobility network-id command in order to configure Layer 3 mobility in a wireless network. This command is meant to be used when the AP participates in a wireless domain services (WDS) infrastructure with a WLAN services module (WLSM) (that acts as the WDS device) where there is Layer 3 mobility.
Therefore, when an AP is configured as a WDS device, do not use the mobility network-id command.
If you use this command incorrectly, connectivity problems in the WLAN network result, such as:
Clients do not get IP addresses from the DHCP.
Clients cannot associate with the AP.
A wireless phone cannot be authenticated when you have a voice-over WLAN deployment.
So, if yur network uses AP as WDS, it doesnt have layer-3 mobility. So, this command will introduce unexpected results.
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
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 ...
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.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...