It sounds like you are describing the correct behavior. From the config guide (see the part of the NOTE: "Wireless clients cannot manage another wireless controller with which they are not associated."):
To enable Cisco Wireless LAN controller management from an associated wireless client, use the config network mgmt-via-wireless command.
NOTE: This feature allows wireless clients to manage only the Cisco Wireless LAN controller associated with the client AND the associated Cisco 1000 series lightweight access point. That is, clients cannot manage another Cisco Wireless LAN controller with which they are not associated.
> I've seen also that I cannot ping the management
> interface from the L3 catalyst the controller is
> connected if the source interface of these ping
> is a VLAN different from the management VLAN.
We're experiencing the same thing with the following adaptation:
- We can't ping the controller's management interface from the L3 Switch if the source interface is different from the management VLAN AND it's one of the wireless VLANs.
- We can ping the controller's management interface from the L3 Switch if the source interface is different from the management VLAN AND if this VLAN is not used for wireless clients.
So, I guess this has to do with the note mentioned above ("Wireless clients cannot manage another wireless controller with which they are not associated.").
=> i.e. the controller can't distinguish whether the ping is from the L3 Switch, a wired PC in that VLAN, or from a wireless client. Consequently, the controller blocks all requests coming from a wireless VLAN but through the LAN interface...?!
Also, the bug-id mentioned above explains why this was working with 22.214.171.124.
Anyway, for me this restriction is a bit strange...
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...