Use of controller template on WCS results in reset of virtual interface
I have observed that when initially implementing a WCS controller template to manage WLC(s) that when you first implement/apply the Controller template that the virtual interface setting for the WLAN gets reset to the management interface.
The result of this is that all the users on that WLAN can't get anywhere because they end up on the wrong VLAN. This could be both a interruption of service issues as well as a potential security issue - because you do not want wireless users having access to the management VLAN.
This behavior is puzzling because the template that was applied had been built automatically by the WCS from the WLC's own existing configuration. All we did was apply it back to the WLC.
Once this WLAN's virtual interface is manually set back to the correct virtual interface and the template is reapplied, the problem is corrected.
Has anyone else experienced this? For those who haven't, you may want to double check your WLAN virtual interfaces after applying the template.
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...