Cisco unified wireless network software release 7.2

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 platfroms:. 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. 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. Configure auto-anchor for WLAN. Connect the client to WLAN through the foreign controller.

Wait till session timeout. 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.

Highlights: Unified Policy: Cisco's approach to moving beyond basic BYOD connectivity provides a unified policy across the organization's entire network — wired, wireless LAN, cellular and VPN — helping set and enforce specific policies across the entire company based on users' roles, the devices they are using, the applications in use, and posture information. With this integration, IT can use Cisco ISE to define policies that help ensure mobile devices are enrolled in MDM, and gain visibility and control over endpoint access based on policies such as requiring a pin lock, disallowing "jailbroken" devices, or remotely wiping the data on lost or stolen devices.

Considering the Connected World Technology Report findings that 70 percent of employees worldwide admit that they break IT policies, with one in five citing the need to access unauthorized programs and applications to get their job done, a unified policy based on both the user needs and company needs will create a more secure work experience that supports employee and IT needs.

VideoStream also allows IT to prioritize video streams efficiently over the wired network. Video scalability is becoming increasingly important, especially when considering the Cisco Visual Networking Index VNI forecast that details how video will account for the majority of overall traffic, with business video conferencing alone increasing sixfold from to More Devices: With this update, one controller can support up to 3, access points and 30, clients, allowing for a flexible, scalable wireless network that can support higher capacities while lowering operational costs.

IPv6 Support: Optimized IPv6 client support with full functionality, providing seamless roaming without drops, improved video and network communication and enhanced IPv6 security protection to close any security holes. Having full IPv6 client functionality is critical to a company's BYOD strategy as 71 percent of smartphones and tablets — 1. Cisco Unified Wireless Network Software 7.

Simplified Operations and Network Management: Cisco offers simplified, centralized operations and network management to understand application performance from a user perspective, accelerate troubleshooting and lower operating costs. This added visibility allows IT to understand and track the user's application performance, quickly spot the exact location of an application performance problem, and correct it on the first try, saving time and money while increasing user satisfaction.

Complete Lifecycle Management: Prime Infrastructure 1. This package provides IT with one place for planning, deployment and on-going management of Cisco infrastructure. Cisco ISE 1. When you are configuring the operating system in controller, you are modifying volatile RAM; you must save the configuration from the volatile RAM to the NVRAM to ensure that the controller reboots in the current configuration.

Knowing which memory you are modifying is important when you are doing the following tasks:. During installation, we recommend that you connect all lightweight access points to a dedicated controller, and configure each lightweight access point for final operation.

This step configures each lightweight access point for a primary, secondary, and tertiary controller and allows it to store the configured mobility group information. During failover recovery, the following tasks are performed:. In multiple-controller deployments, if one controller fails, the access points perform the following tasks:. When sufficient controllers are deployed, if one controller fails, active access point client sessions are momentarily dropped while the dropped access point associates with another controller, allowing the client device to immediately reassociate and reauthenticate.

Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. PDF - Complete Book Updated: July 6, Chapter: Chapter 1 - Overview. NCS has tools to facilitate large-system monitoring and control. Single-Controller Deployments A standalone controller can support lightweight access points across multiple floors and buildings simultaneously and support the following features: Autodetecting and autoconfiguring lightweight access points as they are added to the network.

Full control of lightweight access points. Lightweight access points connect to controllers through the network. The network equipment may or may not provide Power over Ethernet PoE to the access points. Multiple-Controller Deployments Each controller can support lightweight access points across multiple floors and buildings simultaneously. A multiple-controller system has the following additional features: Autodetecting and autoconfiguring RF parameters as the controllers are added to the network.

Same-subnet Layer 2 roaming and inter-subnet Layer 3 roaming. Automatic access point failover to any redundant controller with a reduced access point load see the Cisco Wireless LAN Controller Failover Protection. Operating System Software The operating system software controls controllers and lightweight access points. Wi-Fi protected access WPA dynamic keys. In manual disabling, you block access using client MAC addresses.

In automated disabling, which is always active, the operating system software automatically blocks access to network services for a user-defined period of time when a client fails to authenticate for a fixed number of consecutive attempts.

This feature can be used to deter brute-force login attacks. Operational Requirements The requirement for Layer 3 LWAPP communications is that the controller and lightweight access points can be connected through Layer 2 devices on the same subnet or connected through Layer 3 devices across subnets.

Configuration Requirements When you are operating the Cisco wireless LAN solution in Layer 2 mode, you must configure a management interface to control your Layer 2 communications. Cisco Wireless LAN Controllers When you are adding lightweight access points to a multiple-controller deployment network, it is convenient to have all lightweight access points associate with one master controller on the same subnet.

Controller Platforms Controllers are enterprise-class high-performance wireless switching platforms that support Features Not Supported Wired guest access Cannot be configured as an auto anchor controller.

Cisco Flex Series Controller The Cisco Flex Series Controller enables you to deploy full featured, scalable, and secure FlexConnect network services across geographic locations. Increased resiliency using controller redundancy and FlexConnect Fault Tolerance.

Increased traffic segmentation using FlexConnect central and local switching. Replicates store designs using AP groups and FlexConnect groups. Features include: Connections for up to access points and 15, clients Support for higher client density than other wireless LAN controllers Ability to update access points at once Layer 3 mobility services for video, voice, guest, location, Enterprise Wireless Mesh, and teleworking Advanced wireless security, with Layer 1 wireless intrusion prevention system wIPS capabilities.

However, you can configure it as a foreign controller. Details of the wired connections are as follows: The Cisco Series Controllers connect to the network using up to eight fiber-optic Gigabit Ethernet cables.

The standard CAT-5 cable can also be used to conduct power for the lightweight access points from a network device equipped with Power over Ethernet PoE capability. This power distribution plan can be used to reduce the cost of individual AP power supplies and related cabling.

Power Over Ethernet Lightweight access points can receive power through their Ethernet cables from Knowing which memory you are modifying is important when you are doing the following tasks: Using the configuration wizard Clearing the controller configuration Saving configurations Resetting the controller Logging out of the CLI.

Cisco Wireless LAN Controller Failover Protection During installation, we recommend that you connect all lightweight access points to a dedicated controller, and configure each lightweight access point for final operation.