Difference between Local mode and FlexConnect central switching

[c.andrew]

I'm trying to understand why you'd use FlexConnect "Vlan based central switching", when you could simply use Local mode? Please can anyone explain the difference.

I understand you may have a branch environment, which required two WLANs, one local switched and one centrally switched, but apart from that scenario, why would you choose "Vlan based central switching"?

I've been using the following article to understand this topic:

http://www.cisco.com/en/US/docs/solutions/Enterprise/Mobility/emob73dg/ch7_HREA.html#wp1103053

[Scott Fella]

Guest WLAN that egress at the central HQ. Or when you have buildings that are connected with OptiMAN or GigaMAN and want to tunnel traffic back.

Sent from Cisco Technical Support iPhone App

[c.andrew]

Thanks. But why wouldn't regular "local mode" work in these scenarios?

[Scott Fella]

AP's stay up if they loose connection the the WLC in FlexConnect but not in local mode.

Sent from Cisco Technical Support iPhone App

[c.andrew]

I appreciate your answers, but I must be missing something - please bear with me.

In the URL (linked in my original post), it states that with central auth and central switching, if the link dies:

"Central switched WLANs (above) no longer beacon or respond to probe requests when the FlexConnect AP is in standalone mode. Existing clients are disassociated."

[Scott Fella]

That's using 802.1x. Per shared key will still keep clients. It comes down to loosing the wan. If you loose the wan, do you care about wireless.

Sent from Cisco Technical Support iPhone App

[Scott Fella]

Single WLC and no redundancy, FlexConnect is a good option. You need to understand the limitations to APs running in FlexConnect than in local mode.

Sent from Cisco Technical Support iPhone App

[Scott Fella]

Read about FlexConnect groups.

http://www.cisco.com/en/US/docs/wireless/controller/7.2/configuration/guide/cg_flexconnect.html#wp1225516

Sent from Cisco Technical Support iPhone App

[c.andrew]

Thanks for your help Scott. I'm not in full agreement with all you say, but you have helped me figure it out.

You said the article was related only to 802.1x, but the article states that "802.1X is used in the example, but other mechanisms are equally applicable.".

The article you linked regarding FlexConnect groups also states that central switching is only valid in "connected mode", i.e., when the WAN is up.

However, I have found the following, which kind of explains the purpose of a central switched FlexConnect deployment

http://www.cisco.com/en/US/products/ps11635/products_tech_note09186a0080b7f141.shtml#central

Thanks again.

[Scott Fella]

You asked about local mode vs FlexConnect... Local mode requires the AP and WLC to have connectivity between them.  FlexConnect doesn't.  So when a FlexConnect is operational, it can be Connected or Standalone.  There are limitations to FlexConnect mode when compared to local mode.  The decision on using Flexconnect is simple... is it a remote site and the link isn't a big pipe.  Central switching depends on if you want traffic to tunnel back or not.... if all resources has to come back to HQ, then you centrally switch, if they have services out at the sites, you locally switch.  Authentication is a small piece to this, because, you have to take into consideration if the WAN goes down.

Thanks,

Scott

Help out other by using the rating system and marking answered questions as "Answered"

[Scott Fella · Accepted solution]

Here are the limitation when using FlexConnect compared to local mode

http://www.cisco.com/en/US/docs/wireless/controller/7.2/configuration/guide/cg_flexconnect.html#wp1241304

Thanks,

Scott

Help out other by using the rating system and marking answered questions as "Answered"

[ITexpert]

Thanks Scot,

I understand the difference and need for Flex connect.

I join the new company, I see all APs are in local mode from my WLC but when I go the switch connected with WLC, I saw that interfaces connected with APs are configured with command: switch port trunk allowed vlan guest,staff

According to my understanding interfaces connected with WLC are configured with trunk and interfaces connected with APs are always in access mode and should be accessed in wireless vlan.

On Other switches, APs are connected with ports in default state and nothing is configured like (switch port mode access)

Thanks,

The strange thing is its working ideal.

Thanks