Tags
In this post we will see how L2 Inter Controller Roaming works. I am using the following topology where previously configured for Mobility.(See Configuring WLC Mobility post before this)
Since this is LAB environment, I will disconnect client forcefully from previously associated AP in order to client to go to other AP . This is how I simulate client roaming. I will have active voice call while this roaming event occur & observe whether that call session get dropped while roaming occur.
First we will check the client associations in WLC1.
(WLC1) >show client summary Number of Clients................................ 1 MAC Address AP Name Status WLAN/GLAN Auth Protocol Port Wired ----------------- ----------------- ------------- -------------- ---- ---------------- ---- ----- 00:1b:d4:58:e6:1a LWAP-02 Associated 4 Yes 802.11a 1 No (WLC1) >show client detail 00:1b:d4:58:e6:1a Client MAC Address............................... 00:1b:d4:58:e6:1a Client Username ................................. user2 AP MAC Address................................... 54:75:d0:3e:80:b0 AP Name.......................................... LWAP-02 Client State..................................... Associated Client NAC OOB State............................. Access Wireless LAN Id.................................. 4 BSSID............................................ 54:75:d0:3e:80:bc Connected For ................................... 199 secs Channel.......................................... 161 IP Address....................................... 10.10.14.54 Association Id................................... 1 Authentication Algorithm......................... Open System Reason Code...................................... 1 Status Code...................................... 0 Client CCX version............................... 5 Client E2E version............................... No E2E support Diagnostics Capability........................... Not Supported S69 Capability................................... Not Supported Re-Authentication Timeout........................ 1378 Mirroring........................................ Disabled QoS Level........................................ Platinum 802.1P Priority Tag.............................. 6 WMM Support...................................... Enabled APSD ACs....................................... BK(T/D) BE(T/D) VI(T/D) VO(T/D) Power Save....................................... ON Current Rate..................................... 54.0 Supported Rates.................................. 24.0,36.0,48.0,54.0 Mobility State................................... Local Mobility Move Count.............................. 1 Security Policy Completed........................ Yes Policy Manager State............................. RUN Policy Manager Rule Created...................... Yes ACL Name......................................... none ACL Applied Status............................... Unavailable NPU Fast Fast Notified........................... Yes Policy Type...................................... WPA2 Authentication Key Management.................... CCKM Encryption Cipher................................ CCMP (AES) Management Frame Protection...................... No EAP Type......................................... 0 Interface........................................ vlan14 VLAN............................................. 14
Now we will forcefully remove this client from WLC1. See the below screen how to do this.
I did not noticed call get drop during this roaming event. You can see client entry moved to WLC2 which is normal in L2 Roaming.
(WLC2) >show client detail 00:1b:d4:58:e6:1a Client MAC Address............................... 00:1b:d4:58:e6:1a Client Username ................................. user2 AP MAC Address................................... 64:a0:e7:af:47:40 AP Name.......................................... LWAP-03 Client State..................................... Associated Client NAC OOB State............................. Access Wireless LAN Id.................................. 4 BSSID............................................ 64:a0:e7:af:47:4c Connected For ................................... 31 secs Channel.......................................... 40 IP Address....................................... 10.10.14.54 Association Id................................... 1 Authentication Algorithm......................... Open System Reason Code...................................... 1 Status Code...................................... 0 Client CCX version............................... 5 Client E2E version............................... No E2E support Diagnostics Capability........................... Not Supported S69 Capability................................... Not Supported Re-Authentication Timeout........................ 1743 Mirroring........................................ Disabled QoS Level........................................ Platinum 802.1P Priority Tag.............................. 6 WMM Support...................................... Enabled APSD ACs....................................... BK(T/D) BE(T/D) VI(T/D) VO(T/D) Power Save....................................... OFF Supported Rates.................................. 24.0,36.0,48.0,54.0 Mobility State................................... Local Mobility Move Count.............................. 0 Security Policy Completed........................ Yes Policy Manager State............................. RUN Policy Manager Rule Created...................... Yes ACL Name......................................... none ACL Applied Status............................... Unavailable NPU Fast Fast Notified........................... Yes Policy Type...................................... WPA2 Authentication Key Management.................... CCKM Encryption Cipher................................ CCMP (AES) Management Frame Protection...................... No EAP Type......................................... PEAP Interface........................................ vlan14 VLAN............................................. 14 Quarantine VLAN.................................. 0 Access VLAN...................................... 14
If you take a wireshark packet capture of WLC connected trunk port while roaming occurs you can verify sequence of events.(see below)
In next post we will see how L3 roaming occur.
Related Posts
1. Wireless Mobility Basics
2. Configuring Mobility on WLC
3. L3-Inter Controller Roaming
4. WLC – Web Authentication
5. Configuring Auto Anchor
6. Auto-Anchor Foreign Mapping
7. Mobility Ping Tests
8. Configuring Wired Guest
9. Static IP Clients Mobility
mrn-cciew 
Hi Sir,
I am getting R0Kh unreachable as reason code in authentication response while roaming, Please reply back in which scenario it might happen.
Regards,
Rajaskhar
Hi, not sure exactly what cause it. Since it is FT related msg and R0KH is typically WLC, it is complaining about AP cannot reach WLC.
HTH
Rasika