Scene Introduction
SubnetBits’ network lab, where Sophie approaches Professor Network with a new topic.
Introduction
Good morning, Professor. I’ve been reading about FlexConnect with AireOS. Can you explain how it’s implemented?
Certainly, Sophie. FlexConnect allows APs to switch traffic locally and operate semi-autonomously from the controller. Here’s a high-level overview for AireOS controllers:
- Mode Change: First, change the AP’s mode to FlexConnect.
- Local Switching Configuration: Then, enable local switching on the AP.
- VLAN Configuration: Configure the native VLAN on both the FlexConnect AP and the attached Ethernet switch, and ensure proper WLAN-to-VLAN mapping.
So, the APs can operate independently while still being managed by the controller?
Exactly. They can handle local traffic directly, reducing latency and dependency on the controller for certain operations.
Professor, can you walk me through the detailed steps you mentioned above for configuring FlexConnect in AireOS?
Certainly, Sophie. Let’s break down each step:
- Converting AP to FlexConnect Mode: First, in the AireOS controller, go to Wireless > Access Point > [AP_NAME] > AP Mode, and select FlexConnect. Performing this step will require a reboot from the AP and a warning pop-up message will by displayed.
- Configuring Locally Switched WLANs: Next, for WLANs that will be locally switched at the branch, go to WLANs > [WLAN Name] > Advanced. Here, navigate to the FlexConnect menu and enable FlexConnect Local Switching. Finally click Apply. Keep in mind that on an AP configured in FlexConnect Mode, you can have both centrally and locally switched WALNs. For example, the guest SSID can be locally switch and traffic send directly to the internet, while the Corporate SSID would be centrally switched and the traffic should pass the HQ firewall, as requested by the security policies, before going to the internet.
- Native VLAN and WLAN-to-VLAN Mapping: Finally, on the Wireless menu, a FlexConnect sub-tab appears after changing the mode. Here, enable VLAN Support for trunking on the AP. Configure the native VLAN, then go to VLAN Name Id Mappings and map WLAN IDs to the correct VLAN IDs used on the trunk.
So, the APs can operate independently while still being managed by the controller?
Exactly. They can handle local traffic directly, reducing latency and dependency on the controller for certain operations.