Mobility tunnel impact user onboarding

[syedimteyazahmad]

Hi Team,

We have mobility tunnel between two controllers. When user onboarding happening, is mobility tunnel presence increase extra time for user onboarding like getting IP. 

[JPavonM]

Mobiity tunnel is only used when a device roam from an AP in one controller to an AP in the other controller, so it will have some impact during roaming events, not during the initial onboarding.

[syedimteyazahmad]

Do you have any reference document 

[Flavio Miranda]

@syedimteyazahmad 

Is this tunnel between anchor and foreign WLC?

Some delay would be normal as there will be more overhead but not too much delay

You can run the command  below for testing

mping mobility_peer_IP_address

eping mobility_peer_IP_address

[syedimteyazahmad]

No , we do not have foreign anchor setup . Its simple mobility configuration between two foreign controller.

[Flavio Miranda]

Would be nice to see logs.  Run a debug using some client mac address and try to simulate the problem. Share the logs here for review. 

[Rich R]

 As @JPavonM said it only impacts when a client roams across APs on different WLCs:
https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/config-guide/b_wl_16_10_cg/mobility.html
https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/213913-building-mobility-tunnels-on-catalyst-98.html