having no problems to get the AP's attached and configured via the WLC, but i'm not able to get the DNS-resolution in the LAN done proper.
That means: Having 3 AP's connected to WLC2106, this one is getting it's DNS for one SSID/VLAN from an external DHCP-Server - works very well. If you are connected via a real copper-cable to the VLAN, you'll get the DNS-resolution (put up an ip name-configuration on the DHCP-Server which is a cisco-switch) but via wireless - no chance.
Tried all versions of changing the default-gateway or DNS-Server (directly to the DHCP, where the ip-name-resolution is lying) - nothing.
What the hell? :) It seems really to be a wireless-problem. Allthough i can use external DNS-Servers to get in the internet but getting a local (LAN) solution would be preferrable...
The second idea is it: clients joining without any problem - but not getting the DNS-issues from the LAN - which actually work properly. A DNS-host-entry is configured on the DHCP-Server - which is working with all wireless clients.
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...