We are migrating over 360 WAP to LWAPP and have encountered an issue associated with the env_vars file.
It appears that the env-vars file is referenced during the LWAPP migration tool upgrade process and the env_vars file contains out of date IP information that results in the newly converted LWAPP device having an incorrect IP address of incorrect DNS address.
We have tried deleting the env_vars file without success, as a 'reload' as part of the migration process recreates the dodgy env_vars information.
Is there any way to find the location of the old IP information that is being used by the WAP to create the env_vars file? It is not the running config, as the IP info is years out of date, so it must be hidden somewhere in flash?
Is there a way to find out where and then delete it?
Does anyone else have a solution that does not involve me having to climb a ladder 360 times and physically remove the WAP, perform a local upgrade and then re-install it?
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...