Inter−Platform Mobility; Local Eap Authentication; Link Aggregation (Lag) - Cisco 8500 Series Deployment Manual

Wireless controller

Hide thumbs Also See for 8500 Series:

Table of Contents

Note: Multicast−Unicast is required for IPv6 operation on FlexConnect APs (for RA and NS packet delivery).

Inter−Platform Mobility

In most networks, support for heterogeneous Wireless Controllers in a mobility group is usually required.

These can be instances of upgrade, migration, or backup with such a heterogeneous configuration. In these

cases, the number of supported Fast Secure Roaming (FSR) clients should be considered in the network

design. For example, consider a large wireless network composed of a mix of the following WLC platforms,

all configured in the same mobility group:

•

8500 (supports FSR for 64,000 clients)

•

7500 (supports FSR for 64,000 clients)

•

WiSM2 (supports FSR for 30,000 clients)

•

5500 (supports FSR for 14,000 clients)

In this scenario:

64,000 authenticated clients can seamlessly roam back and forth between the 7500s and the 8500s.

30,000 authenticated clients can seamlessly roam back and forth between multiple WiSM2

controllers, or between a WiSM2 to 8500 or 7500 controllers.

14,000 authenticated clients can seamlessly roam back and forth between multiple 5500 controllers,

or between a 5500 to a WiSM2, 8500, or 7500 controllers.

Wireless clients exceeding those limits will require a rejoin after session timeout.

The Local EAP authentication database does not scale to the supported 64,000 Clients on the 8500 Controller.

Although the feature to have the 8500 act as an Authentication Sever has not been disabled in the user

interface, its purpose is solely to support test setup, and not for production deployment.

LAG across the 2x10G interfaces is supported in software versions 7.4 and later. The LAG configuration

allows for an active−active link operation with fast failover link redundancy.

Table of Contents