Advertisement
FlexConnect Groups
FlexConnect Groups
Figure 8
In most typical branch deployments, it is easy to foresee that client 802.1X authentication takes place
centrally at the Data Center as shown in
these concerns:
•
•
•
•
FlexConnect Group is primarily designed and should be created to address these challenges. In addition,
it eases organizing each branch site, because all the FlexConnect access points of each branch site are
part of a single FlexConnect Group.
Note
Primary Objectives of FlexConnect Groups
Backup RADIUS Server Failover
You can configure the controller to allow a FlexConnect access point in standalone mode to perform full
802.1X authentication to a backup RADIUS server. In order to increase the resiliency of the branch,
administrators can configure a primary backup RADIUS server or both a primary and secondary backup
RADIUS server. These servers are used only when the FlexConnect access point is not connected to the
controller.
Note
Flex 7500 Wireless Branch Controller Deployment Guide
20
Central Dot1X Authentication (Flex 7500 Acting as Authenticator)
How can wireless clients perform 802.1X authentication and access Data Center services if Flex
7500 fails?
How can wireless clients perform 802.1X authentication if WAN link between Branch and Data
Center fails?
Is there any impact on branch mobility during WAN failures?
Does the FlexConnect Solution provide no operational branch downtime?
FlexConnect Groups are not analogous to AP Groups.
Backup RADIUS accounting is not supported.
Figure
8. Because the above scenario is perfectly valid, it raises
Advertisement
