Wireless client cannot associate to an access point after a firmware upgrade
The firmware has recently been upgraded and there is no connectivity to the access point. Incorrect versions of the client software, including drivers, firmware, and utilities may be the root cause of this problem.
To resolve this problem:
Upgrade the firmware again and then reboot the client machine after upgrade.
Upgrade Cisco IOS through the GUI:-
Check the current software version of the AP. Open a browser and type http://<ip address of the ap> in the address bar in order to log into the GUI. On the main page, click on the System Software menu from the left hand side. Choose the Software Upgrade option and check the current Cisco IOS version from the System Software Version field.
Note: Refer to Cisco Software Downloads FAQ for information on how to download firmware from Cisco.com Downloads.
From the software upgrade page, choose TFTP upgrade, as shown in Figure.
Note: You can also check the Cisco IOS version from this screen.
Enter the IP address of the TFTP server.
Specify the name of the Cisco IOS software file to be upgraded in the Upgrade System Software Tar file field, as shown in Figure.
Note: In order to have a smooth upgrade, do not change the original Cisco IOS filename. Leave the name as it was when you downloaded the file from cisco.com.
Click the Upgrade button. A status window similar to the one shown in Figure appears.
This takes few minutes, and then the AP reboots once the upgrade is complete.
This section describes how to upgrade Cisco IOS on an access point through the CLI.
Log into the access point through a Telnet session.
You can download a new image file and choose to replace the current image or keep the current image.
Note: The latter option is helpful when one of the Cisco IOS files are corrupted. You can work with the access point from the other image in the flash.
If you choose to overwrite the existing file, issue the archive download-sw /overwrite /reload tftp: //location/image-name command.
The /overwrite option overwrites the software image in flash with the downloaded image. The /reload option reloads the system after you download the image unless the configuration is changed and not saved. For //location, specify the IP address of the TFTP server. For image name, specify the Cisco IOS filename that you plan to use to upgrade the access point. In this example, the command is archive download-sw /overwrite /reload tftp: //10.77.244.194/c1240-k9w7-tar.124-10b.JA3.tar. As mentioned earlier, do not change the name of the Cisco IOS file. Leave it as the default. You find these logs during the successful file transfer:
Loading c1240-k9w7-tar.124-10b.JA3.tar from 10.77.244.196 (via BVI1): !
New software image installed in flash:/c1240-k9w7-mx.124-10b.JA3.
Configuring system to use new image...done.
Requested system reload in progress...
If you choose to keep the existing file, issue the archive download-sw /leave-old-sw /reload tftp://location/image-name command. If there is not enough space to install the new image and keep the current running image, the download process stops, and an error message is displayed.
The AP downloads the Cisco IOS file specified from the DHCP server and reloads with the new software.
2. If possible uninstall the Client software completely and install Aironet Client Bundle which has Firmware, Drivers and Utility bundled together. Upgrade the firmware using that.
3. Check basic settings such as SSID , Security options, Power Settings , Data Rates
Note: If the client card has been working before upgrading please downgrade it back to the version it was working. Please do not upgrade unless and otherwise it is really needed.
For more information on the compatibility of the software, refer to the release notes located at Wireless LAN Cisco Downloads.
WLAN adapters (wireless card) / ACU (Aironet Client Utility)
Hi,I configured two switch Catalyst 9300 as a Embedded Wireless Controller (9800) in the DNA Center server version 220.127.116.11 in fabric mode.MY question, how to keep high availability in two Embedded Wireless controllers is we using the concept N+...
Hi board,assuming in a WLC C9800 SSO cluster with RMI (SW version 17.3.3), you want to replace a failed cluster member... what is the preferred way to do it?I tried the following and it was a disaster:Assuming chassis2 has failed completely and needs to b...
Hi. AP does not join WLC.The AP tries to join the WLC, but the session does not appear to be established.Attach debug content. May 11 08:13:09 kernel: [*05/11/2021 08:13:09.8076] CAPWAP State: DiscoveryMay 11 08:13:09 kernel: [*05/11/2021 ...
Hi, I am going to disable low data rates on WLC:802.11a (6,9,12,18)802.11b (1,2,5.5,6,9,11) And I have two questions. We have hundreds of devices and checking the data rates on each of them individually is impossible. Is there any way to se...
Platform: 9800-L-FSoftware: 17.3.2a SSID:WPA(AES/TKIP)+WPA2(AESCCMP128) running simple PSK authentication. No L3 Auth involved. The DHCP forwarding is orchestrated by the 9800 via the SVI. After scouring the configuration and comparing 9800...