Buy or Renew
Buy or Renew
Cisco Virtual Engineer generative AI bot now active in Wireless Discussion Forum. Learn more.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
6684
Views
15
Helpful
2
Replies

Flex+bridge mesh question

Go to solution
Kashim_Tr
Level 1
Level 1

‎11-08-2017 06:24 AM - edited ‎07-05-2021 07:49 AM

Hello,
I have question to wich i can't find answer. When we have flexconnect AP and it lose wlc it still can handle authentification localy and forward traffic. Can MAP be configured this way too ? So when wlc is down MAP clients can reach resources behind RAP ? Is there any documentation that describe this scenario ?

1 person had this problem
Labels:
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Vengatesa Prasath
Cisco Employee
Cisco Employee

‎11-08-2017 06:47 AM

Hi Kashim_Tr,

 

Hope this helps:

The following are the bridging features for Flex + Bridge mode:

  • The Flex + Bridge mode supports the centrally switched 802.11 WLAN. Traffic for this tunneled WLAN is forwarded to and from a CAPWAP controller over an IP tunnel.

     

  • The Flex + Bridge mode supports the Root Ethernet VLAN Bridging. A root AP bridges the traffic for bridged 802.11 WLANs and secondary Ethernet LANs to a local Ethernet LAN over its root Ethernet port.

     

  • The Flex + Bridge mode bridging is supported on Secondary Ethernet Access Ports and Secondary Ethernet VLAN Trunk Ports.

     

  • Fault Tolerant Resilient Mode enables an AP to continue bridging traffic when the connection to the CAPWAP controller is lost. Both mesh and non-mesh root APs continue to bridge traffic. A child mesh AP (MAP) maintains its link to a parent AP and continues to bridge traffic till the parent link is lost. A child mesh AP cannot establish a new parent or child link till it reconnects to the CAPWAP controller. Existing wireless clients on the locally switching WLAN can stay connected with their AP in this mode. Their traffic will continue to flow through the Mesh and wired network. No new or disconnected wireless client can associate to the Mesh AP in this mode.

     

  • You can configure a separate set of security ACLs for each VLAN that is configured for an Ethernet root port. In a mesh network, only root APs (RAPs) have an Ethernet root port.

     

  • VLAN transparent bridging is not supported on Flex + Bridge mode. You must enter a set of allowed VLAN IDs for each secondary Ethernet trunk port.

     

  • Path Control Protocol to create or delete path instances is supported on the Flex + Bridge mode.

     

  • In a mesh network, a child mesh AP (MAP) inherits local WLAN/VLAN ID bindings, for bridged WLANs, and local secondary Ethernet access port/VLAN ID bindings. The bindings are inherited from the root AP (RAP) via path control messages. Bindings are required in a multi-hop mesh links to support FlexConnect capabilities in Mesh APs.

 

You can find more information for link:

https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-2/config-guide/b_cg82/b_cg82_chapter_010010101.html#concept_61FDD35A8F394244B5CAA21CC906F748

 

 

************** Please rate Useful post**************

View solution in original post

2 Replies 2

Go to solution
Vengatesa Prasath
Cisco Employee
Cisco Employee

‎11-08-2017 06:47 AM

Hi Kashim_Tr,

 

Hope this helps:

The following are the bridging features for Flex + Bridge mode:

  • The Flex + Bridge mode supports the centrally switched 802.11 WLAN. Traffic for this tunneled WLAN is forwarded to and from a CAPWAP controller over an IP tunnel.

     

  • The Flex + Bridge mode supports the Root Ethernet VLAN Bridging. A root AP bridges the traffic for bridged 802.11 WLANs and secondary Ethernet LANs to a local Ethernet LAN over its root Ethernet port.

     

  • The Flex + Bridge mode bridging is supported on Secondary Ethernet Access Ports and Secondary Ethernet VLAN Trunk Ports.

     

  • Fault Tolerant Resilient Mode enables an AP to continue bridging traffic when the connection to the CAPWAP controller is lost. Both mesh and non-mesh root APs continue to bridge traffic. A child mesh AP (MAP) maintains its link to a parent AP and continues to bridge traffic till the parent link is lost. A child mesh AP cannot establish a new parent or child link till it reconnects to the CAPWAP controller. Existing wireless clients on the locally switching WLAN can stay connected with their AP in this mode. Their traffic will continue to flow through the Mesh and wired network. No new or disconnected wireless client can associate to the Mesh AP in this mode.

     

  • You can configure a separate set of security ACLs for each VLAN that is configured for an Ethernet root port. In a mesh network, only root APs (RAPs) have an Ethernet root port.

     

  • VLAN transparent bridging is not supported on Flex + Bridge mode. You must enter a set of allowed VLAN IDs for each secondary Ethernet trunk port.

     

  • Path Control Protocol to create or delete path instances is supported on the Flex + Bridge mode.

     

  • In a mesh network, a child mesh AP (MAP) inherits local WLAN/VLAN ID bindings, for bridged WLANs, and local secondary Ethernet access port/VLAN ID bindings. The bindings are inherited from the root AP (RAP) via path control messages. Bindings are required in a multi-hop mesh links to support FlexConnect capabilities in Mesh APs.

 

You can find more information for link:

https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-2/config-guide/b_cg82/b_cg82_chapter_010010101.html#concept_61FDD35A8F394244B5CAA21CC906F748

 

 

************** Please rate Useful post**************

Go to solution
Kashim_Tr
Level 1
Level 1
In response to Vengatesa Prasath

‎11-08-2017 07:05 AM

Thank you. That probably answer to my question. No local authentication on MAP
0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking for a $25 gift card