cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
266
Views
2
Helpful
2
Replies

Client Roaming Across Policy Profile

hanateaa
Level 1
Level 1

Hello everyone,

I'm currently managing a Cisco 9800-40 WLC running on version 17.9.4a, and I'm facing a client roaming issue. When clients attempt to roam, I receive a message indicating that the client was deleted with the reason "roam across policy profile deny." After some research, I came across to this article Client Roaming Across Policy Profile suggesting that enabling "wireless client vlan-persistent" could allow for seamless roaming across policy profiles.

However, I still have some questions. In our setup, we have a WLAN with different site tags and policy profile configurations:

Site Tag A is using Policy Profile A with Central Switching.

Site Tag B is using Policy Profile B with FlexConnect.

If I enable Roaming Across Policy Profiles, will there be any impact on WLANs with differing configurations like the ones I described above?

Any insights or advice on potential issues or considerations would be greatly appreciated. Thanks in advance!

2 Replies 2

marce1000
VIP
VIP

 

  - There isn't any impact on the individual WLANs but the roaming across a standard policy profile and a flex policy profile is not supported. 
       It's advisable to always have a checkup of the  9800-40 WLC configuration with the CLI command
       show tech wireless  (not  simple 'show tech') and feed the output from that into Wireless Config Analyzer
                         Important errors , also related to this topic will always get reported , 

 M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

jagan.chowdam
Spotlight
Spotlight

When you enable local switching on policy profile for FlexConnect APs, the APs perform local switching. However, for the APs in local mode, central switching is performed.

In a scenario where the roaming of a client between FlexConnect mode AP and Local mode AP is not supported, the client may not get the correct IP address due to VLAN difference after the move. Also, L2 and L3 roaming between FlexConnect mode AP and Local mode AP are not supported.

Ref: https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-9/config-guide/b_wl_17_9_cg/m_vewlc_flex_connect.html

 

Jagan Chowdam

/**Pls rate useful responses**/

Review Cisco Networking for a $25 gift card