Tags: Latest Contents. Upgraded code to 8. Created by sherielbailey on AM. Unable to gain access to an Aironet Created by netmon on PM. Hi everyone,I bought a used Aironet but I'm unable to gain access to it. I have it connected with a PoE injector " The AP powers up with a blinking green light, then sets on a green-red-off pattern which I understa Created by acapistran96 on PM.
I've been trying to rack my mind about what is going on with this AP. If it helps any I'll describe my setup. The port on the S is setup w Reason: VLAN not con Created by zzman55 on PM. I'm configuring a new wireless network using as a controller and I access point. Created by Wes Schochet on AM. Looking to implement the same functionality on the Is this ju Ask a Question. Find more resources.
Project Gallery. New Community Member Guide. The management interface acts like an AP-manager interface by default, and the access points can join on this interface. Note An AP associated with the controller in local mode should be converted to FlexConnect mode or Monitor mode, either manually or by enabling the autoconvert feature.
On the Flex controller CLI, enable the autoconvert feature by entering the config ap autoconvert enable command. The following sections lists Open Caveats and Resolved Caveats for Cisco controllers and lightweight access points for version 7. These caveat titles are not intended to be read as complete sentences because the title field length is limited.
In the caveat titles, some truncation of wording or punctuation might be necessary to provide the most complete and concise description. The only modifications made to these titles are as follows:. Note If you are a registered cisco. Table lists open caveats in controller software release 7. Controller does not respond during a task with IPv6 traffic. Symptom : Controller might unexpectedly reboot with crash information that is similar to the following:.
Analysis of Failure:. Software was stopped for the following reason:. Conditions : Controller is handling IPv6 traffic. The controller does not respond to SNMP requests if the source address of the request comes from a subnet that is configured as a dynamic interface. Certain IP addresses used for management interfaces result in AP join issues. Symptom : When using VLSM, if the fourth octet of the management IP address is the same as the fourth octet of the broadcast address of another interface on the controller, the controller fails to respond to LAP discoveries.
For example, if the management interface IP address is Workaround : Change the IP address of the management interface. Symptom : Controller unresponsive and reboots unexpectedly. Ad hoc rogues are not shown in the controller after their status is changed to internal.
Symptom : If the status of the detected ad hoc rogues is changed to internal, users cannot see the MAC address of the ad hoc rogues in the controller. Further Problem Description : Unable to locate the MAC address of the ad hoc rogue using the show run-config command and in the configuration XML file of the controller. Controller AP list shows previously connected access points. Symptom : A Cisco Controller erroneously lists disconnected access points on the AP summary list.
Conditions : Under normal operation, an access point previously registered on a Cisco Controller running 6. However, the AP is still shown on the AP summary list. Idle status on show client ap Symptom : When the show client ap The show run-config command displays wrong command syntax.
Symptom : The show run-config command displays commands that are no longer active and commands with incorrect syntax. Conditions : Controller software Release 7.
Workaround : The following options are available:. Symptom : When two wireless clients that are associated with APs on the same controller try to communicate, one client may not pass traffic to the other client. Conditions : L3 roam within controller. For example:. This will result in a failure of communication ARP between this client and another client that is in VLAN1 but that is local to controller2.
Symptom : Although the config wlan security wpa akm cckm timestamp-tolerance msec wlan-id command is configured to a nondefault value, the information about the CCKM timestamp tolerance is not displayed in the output of the show run-config command. Controller might fail to transfer or save configuration and then becomes unresponsive. Symptom : The controller might display the following errors when attempting to transfer or back up the configuration, and eventually reboots without storing a crash file:.
After shutting down the controller ports, the same message is displayed even when there is no AP associated with the controller. Cisco Controller does not set Symptom : Cisco Controller does not set the configured The controller only sets the When the AP receives the packet and sends it over the air, the Wireless to wireless traffic on the same controller does not have a proper downstream marking.
APs unresponsive due to unexpected exception to CPUvector. Symptom : AP on Conditions : Under heavy multicast traffic, the AP has this issue while trying to clean up multicast packet queue. Packet buffers are freed more than once to cause this issue. This can occur randomly with different APs at different times. Workaround : Avoid heavy multicast traffic. The MAP might need reboot to recover. Conditions : The issue can be reproduced consistently in the lab in the following conditions:.
Two controllers: one primary and one backup. Primary controller is disconnected from the network. All APs associate with the backup controller, with the same mesh tree. After n minutes, the primary controller is brought back online, and fallback is enabled.
It is observed that APs move back to associate with the primary controller. Workaround : Disable AP fallback so that if there is a failure, recovery can be done in a controlled manner. Symptom : On a controller software Release 7.
This results in the following message logged on the msglog:. Lag wih CDP does not show all the physical ports correctly. Symptom : CDP neighbors on the switch, where controller is connected to, does not display correct port information. Conditions : LAG is enabled on the controller and CDP is enabled on both sides and on the controller, number of ports connected are either 3, 5, 6 or 7.
Symptom : While booting up, the following error message appears on the attached monitor or on a serial console as follows:. When the Space key is pressed, the system does not boot from the disk. Conditions : Cisco Flex Series Controller, which went through an accidental power interruption, that is, the power plug was pulled while the system was operational. Upon reboot, the RAID card could not find its configuration in the flash memory and therefore it could not boot.
There are two versions of this:. The CLI version can be accessed from the serial console. A prompt is displayed for this on the serial console soon after the error message is displayed.
Further Problem Description : When the Space key is pressed, the system does not boot from the disk. It appears that it has lost the RAID configuration that was present in the system. The controller went through an accidental power interruption, that is the power plug was pulled while the system was operational.
Upon reboot, the RAID card did not find its configuration in the flash memory and therefore it could not boot. The flash configuration was corrupted or erased due to the power interruption. The RAID card keeps a backup of the configuration on the hard drives. However, when the card loses the configuration information in the flash, it does not automatically pick up the backup configuration information from the hard drives.
At this time, the system waits for users to take action. All the data on the hard drives are still intact. Inconsistent limitation of characters for guest username. This, however, is stated as a limitation for guest account usernames in the configuration guide. Creation of default SNMP entries with nondefault values is denied. Workaround : Reconfigure the controller after restoring by entering this command:. However, when the clients want to check the traffic of clients, values are not displayed as expected on the accounting packets.
Symptom : After a web authenticated client roamed from LAP1 associated with controller1 to LAP2 associated with controller2 , the client required web authentication again. The following is didsplayed:. Enter the show traplog command. The following is displayed:. Enter the show msglog command. The following is displayed;. Conditions : Cisco Controller running controller software Release 7. Workaround : Use local user account on the controller.
Cisco WiSM2 may reset under prolonged and very high client roaming conditions. Symptom : Crash file has an output similar to the following:. Workaround : Avoid use of local authentication in large deployments. We recommend that you use external AAA server for large deployments. Further Problem Description : This condition occurred under prolonged, high client roaming conditions approximately 25 to 30 minutes with the maximum number of clients associated with the controller.
This is not a supported deployment scenario in which local authentication is configured for use by clients and roaming is simulated at the rate of roams per second. Retry count of Symptom : After AP is reset, connect one client and initiate constant ping to the gateway. The retry count of This makes the statistics incorrect if users try to investigate retry percentage. The other counters might also be incorrect. It does not appear to be consistent with what is shown in the output of the show controller do1 command if there is SSH into the AP.
Symptom : Wireless multicast message delivery delay of around 5 to 10 seconds. When sh wlan apgroups is generated, an error message is generated in syslog for all nondefault group APs. Error message is incorrect.
This can be tested for any AP on the nondefault group. Error message is sent to syslog, not to buffered logging sh msglog , regardless of level, should be sent to both if using the same error level. Error message does not show which is the wrong AP. Thus, it is difficult to determine the issue and correct because of incomplete data to troubleshoot. Conditions : Command is entered. Workaround : None required.
This issue has no effect on the AP group. Workaround : Options include the following:. Symptom : It is observed that the switch learns a lot of client MAC entries from the management interface of the controller. This traffic sent between the time the controller moves the client into RUN state and the AP being informed of this causes the packets from the locally switched client to egress the controller.
Symptom : Expired client sessions stales on the anchor controller. Connect the client to WLAN through the foreign controller. Although anchor is notified about the expired session and deletes the entries based on debugs, for some client entries, the session stales on the anchor. Those entries cannot be cleared and results in increased current session time.
Workaround : Reboot the controller to clear the 'stale' entries. APs in Local mode reboot; watchdog timer expired. Symptom : APs restart and return with the following message:. Symptom : When disabling data rates or changing a rate to mandatory, the output keyword from the show run-config commands contains an upper case letter, which the CLI parser does not accept.
Conditions : The following output is displayed:. Workaround : Use the command in the following manner:. Symptom : On the output of the data rate commands, any changes in the mandatory rates should be output before disabled rates. If the disabled commands disable all the mandatory rates, the final disable command is rejected until the new mandatory rate is set.
Workaround : Configure in the following order:. Conditions : The DCA and band select commands are not displayed in the output of show run-config commands. Symptom : If RADIUS servers are assigned nonsequential index numbers, some of the output in the show run-config commands have the wrong index numbers. Note The index number used on the final 3 lines are 1, 2, and 3 instead of 3, 4, and 5.
Symptom : Some commands allow for imbedded spaces by including the parameter in quotes. The output from the CLI does not include the quotes. Therefore, the command is invalid. For example, wlan create and wlan apgroup add are such commands. Conditions : The following is the input:. Workaround : Manually add the quotes for names with spaces. The output of the show run-config commands does not include this prompt. Conditions : For example, configuring an AP global syslog host.
Workaround : Proceed without any confirmation. Symptom : Line-feeds are missing on some lines when you enter show run-config commands.
The show client detail mac-addr command does not display client statistics values. Symptom : Only 6 Mbps rate is configured as mandatory on Controller allows creation of dynamic interfaces with overlapping subnet.
Users must ensure that there are no multiple VLANs with overlapping subnets, which might cause issues with Layer 3 roaming of clients. Controller unresponsive when executing the show ap eventlog ap-name command. Symptom : Controller reboots with crash file created while executing the show ap eventlog ap-name command. Symptom : Wired clients are unable to reach wireless clients due to receiving incorrect MAC information from the controller.
Obtaining Documentation and Submitting a Service Request. These release notes describe what is new in this release, instructions to upgrade to this release, and open and resolved caveats for this release. Note Unless otherwise noted, all of the Cisco Wireless LAN controllers are referred to as controllers, and all of the Cisco lightweight access points are referred to as access points. These release notes contain the following sections:. Note For more information on the compatibility of wireless software components across releases, see the Cisco Wireless Solutions Software Compatibility Matrix.
Note Client and tag licenses are required to get contextual such as location information within the context-aware software. Note Before you use an AP series lightweight access point with controller software release 7. M or later releases. The following controller platforms are not supported for the 7. This section provides a brief description of what is new in this release.
Due to this limitation, clients cannot send association requests to WLANs. These clients, however, can still associate with non Clients that are The workaround is to enable or upgrade the driver of the legacy clients to work with the new It is not supported in 7. Downgrading 7. Table lists the controller software releases that support specific Cisco access points. The First Support column lists the earliest controller software release that supports the access point.
For access points that are not supported in ongoing releases, the Last Support column lists the last release that supports the access point. Table Software Support for Access Points. Note The Cisco Access Point was introduced in 7. If your network deployment uses Cisco Access Points with release 7. All other reg. These access points are supported in the separate 4. These access points are not supported in the 4.
If you attempt to download the 7. Enter 1 to run the current software, enter 2 to run the previous software, enter 4 on a series controller , or enter 5 on another controller platform to run the current software and set the controller configuration to factory defaults.
Do not choose the other options unless directed to do so. Note See the Installation Guide or the Quick Start Guide for your controller for more details on running the bootup script and power-on self-test.
With the backup image stored before rebooting, be sure to choose Option 2: Run Backup Image from the boot menu to boot from the backup image. Then, upgrade with a known working image and reboot the controller. This is the default. Note To avoid stranding APs, you must disable AP link-latency if enabled before you use the disable option for the config network ap-discovery nat-ip-only command.
To disable AP link-latency, use the config ap link-latency disable all command. Note Predownloading a 7. If predownloading is attempted to a Cisco Aironet access point, an AP disconnect will occur momentarily. Step 1 Upload your controller configuration files to a server to back them up. Step 2 Follow these steps to obtain the 7. Choose Wireless from the center selection window. Depending on your controller platform, click one of the above options.
Click the controller model number or name. The Download Software page is displayed. Click a controller software release. The software releases are labeled as follows to help you determine which release to download:. Click a software release number. Click the filename filename.
Click Download. Save the file to your hard drive. Repeat steps a through k to download the remaining file. Step 3 Copy the controller software file filename. Step 4 Optional Disable the controller Note For busy networks, controllers on high utilization, or small controller platforms, we recommend that you disable the Step 7 From the File Type drop-down list, choose Code.
Step 10 If you are using a TFTP server, the default values of 10 retries for the Maximum Retries text field, and 6 seconds for the Timeout text field should work correctly without any adjustment. However, you can change these values if desired. To do so, enter the maximum number of times that the TFTP server attempts to download the software in the Maximum Retries text box and the amount of time in seconds that the TFTP server attempts to download the software in the Timeout text box.
Step 11 In the File Path text box, enter the directory path of the software. Step 12 In the File Name text box, enter the name of the software file filename. Step 13 If you are using an FTP server, follow these steps:. The default value is Step 14 Click Download to download the software to the controller. A message appears indicating the status of the download. Step 15 After the download is complete, click Reboot. Step 16 If prompted to save your changes, click Save and Reboot.
Step 17 Click OK to confirm your decision to reboot the controller. Step 18 After the controller reboots, repeat Step 6 to Step 17 to install the remaining file. Step 21 If you have disabled the Step 22 To verify that the 7. Consult your local government regulations to ensure that DTLS encryption is permitted. The following table lists the Paper PAK licenses and their descriptions including their part numbers.
Complete the remaining steps to generate the license file. The license file information will be sent to you in an e-mail. After the installation of the DTLS license, reboot the system. Ensure that the DTLS license that is installed is active. Note If you have a 7. Choose Cisco Series Controller from the right selection box.
From the left navigation pane, click the software release number for which you want to install the non-LDPE software. Step 2 Copy the controller software file filename. This section describes the interoperability of the version of controller software with other client devices. Table describes the configuration used for testing the clients.
Table Test Bed Configuration for Interoperability. Connectivity, traffic, and roaming between two access points.
Table lists the client types on which the tests were conducted. The clients included laptops, handheld devices, phones, and printers. This section lists the features that are not supported in the following platforms:. Note Directly connected APs are supported only in Local mode. The management interface acts like an AP-manager interface by default, and the access points can join on this interface.
Note An AP associated with the controller in local mode should be converted to FlexConnect mode or Monitor mode, either manually or by enabling the autoconvert feature.
On the Flex controller CLI, enable the autoconvert feature by entering the config ap autoconvert enable command. The following sections lists Open Caveats and Resolved Caveats for Cisco controllers and lightweight access points for version 7. These caveat titles are not intended to be read as complete sentences because the title field length is limited.
In the caveat titles, some truncation of wording or punctuation might be necessary to provide the most complete and concise description. The only modifications made to these titles are as follows:. Note If you are a registered cisco. Table lists open caveats in controller software release 7. Controller does not respond during a task with IPv6 traffic. Symptom : Controller might unexpectedly reboot with crash information that is similar to the following:.
Analysis of Failure:. Software was stopped for the following reason:. Conditions : Controller is handling IPv6 traffic. The controller does not respond to SNMP requests if the source address of the request comes from a subnet that is configured as a dynamic interface. Certain IP addresses used for management interfaces result in AP join issues. Symptom : When using VLSM, if the fourth octet of the management IP address is the same as the fourth octet of the broadcast address of another interface on the controller, the controller fails to respond to LAP discoveries.
For example, if the management interface IP address is Workaround : Change the IP address of the management interface. Symptom : Controller unresponsive and reboots unexpectedly. Ad hoc rogues are not shown in the controller after their status is changed to internal. Symptom : If the status of the detected ad hoc rogues is changed to internal, users cannot see the MAC address of the ad hoc rogues in the controller. Further Problem Description : Unable to locate the MAC address of the ad hoc rogue using the show run-config command and in the configuration XML file of the controller.
Controller AP list shows previously connected access points. Symptom : A Cisco Controller erroneously lists disconnected access points on the AP summary list. Conditions : Under normal operation, an access point previously registered on a Cisco Controller running 6. However, the AP is still shown on the AP summary list. Idle status on show client ap Symptom : When the show client ap The show run-config command displays wrong command syntax.
Symptom : The show run-config command displays commands that are no longer active and commands with incorrect syntax. Conditions : Controller software Release 7. Workaround : The following options are available:. Symptom : When two wireless clients that are associated with APs on the same controller try to communicate, one client may not pass traffic to the other client.
Conditions : L3 roam within controller. For example:. This will result in a failure of communication ARP between this client and another client that is in VLAN1 but that is local to controller2.
Symptom : Although the config wlan security wpa akm cckm timestamp-tolerance msec wlan-id command is configured to a nondefault value, the information about the CCKM timestamp tolerance is not displayed in the output of the show run-config command. Controller might fail to transfer or save configuration and then becomes unresponsive. Symptom : The controller might display the following errors when attempting to transfer or back up the configuration, and eventually reboots without storing a crash file:.
After shutting down the controller ports, the same message is displayed even when there is no AP associated with the controller. Cisco Controller does not set Symptom : Cisco Controller does not set the configured The controller only sets the When the AP receives the packet and sends it over the air, the Wireless to wireless traffic on the same controller does not have a proper downstream marking.
APs unresponsive due to unexpected exception to CPUvector. Symptom : AP on Conditions : Under heavy multicast traffic, the AP has this issue while trying to clean up multicast packet queue. Packet buffers are freed more than once to cause this issue. This can occur randomly with different APs at different times. Workaround : Avoid heavy multicast traffic. The MAP might need reboot to recover. Conditions : The issue can be reproduced consistently in the lab in the following conditions:.
Two controllers: one primary and one backup. Mesh tree is R1-M1, R2-M2. Primary controller is disconnected from the network. All APs associate with the backup controller, with the same mesh tree. After n minutes, the primary controller is brought back online, and fallback is enabled. It is observed that APs move back to associate with the primary controller. Workaround : Disable AP fallback so that if there is a failure, recovery can be done in a controlled manner.
Symptom : On a controller software Release 7. This results in the following message logged on the msglog:. Lag wih CDP does not show all the physical ports correctly.
Symptom : CDP neighbors on the switch, where controller is connected to, does not display correct port information. Conditions : LAG is enabled on the controller and CDP is enabled on both sides and on the controller, number of ports connected are either 3, 5, 6 or 7. Symptom : While booting up, the following error message appears on the attached monitor or on a serial console as follows:. When the Space key is pressed, the system does not boot from the disk. Conditions : Cisco Flex Series Controller, which went through an accidental power interruption, that is, the power plug was pulled while the system was operational.
Upon reboot, the RAID card could not find its configuration in the flash memory and therefore it could not boot. There are two versions of this:.
The CLI version can be accessed from the serial console. A prompt is displayed for this on the serial console soon after the error message is displayed. Further Problem Description : When the Space key is pressed, the system does not boot from the disk. It appears that it has lost the RAID configuration that was present in the system. The controller went through an accidental power interruption, that is the power plug was pulled while the system was operational.
Upon reboot, the RAID card did not find its configuration in the flash memory and therefore it could not boot. The flash configuration was corrupted or erased due to the power interruption. The RAID card keeps a backup of the configuration on the hard drives. However, when the card loses the configuration information in the flash, it does not automatically pick up the backup configuration information from the hard drives.
0コメント