Chap 19 - Wireless Roaming and Location Svcs Flashcards
What is Intracontroller Roaming?
When a client roams between LWAPs connected to the same WLC.
How long does an Intracontroller Roam take?
Less than 10 msec
What 2 things might happen when a wireless client re-associates?
- Client might renew its DHCP IP address assignment
- Client might need to re-authenticate (802.1x)
What 3 techniques do controllers offer to streamline key exchanges during roam?
- Cisco Centralized Key Management (CCKM)
- Key caching
- 802.11r
What is Cisco Centralized Key Management (CCKM)
One controller maintains a database of clients and keys on behalf of its APs and provides them to other controllers and their APs as needed during client roams.
What is Key Caching?
What is it?
What are 2 limitations?
- Each client maintains in cache a list of keys used with prior AP associations and presents them as it roams. The destination AP must be present in this list.
- The list is limited to key entries from 8 prior APs.
- Client must have a supplicant
What is 802.11r ?
How does this help a client roam?
What else can the client maintain?
What does the client need to have?
- Client caches a portion of the authentication server’s key and presents that to future APs as it roams. This makes roaming much faster.
- The client can also maintain its QoS parameters as it roams
- Client must have supplicant
What is Intercontroller Roaming?
Roaming between APs on different controllers
What is a Intercontroller Layer 2 roam?
What stays the same on the client?
How long does this roam take?
- Client roams but stays on the same VLAN and Subnet
- Client keeps same IP address
- Fast - less than 20 msec (10 msec for Intracontroller roam)
What happens in a Layer 3 Roam?
- Client roams to different AP w/different controller that is on a different subnet *
- Original controller (anchor controller) and Foreign controller build a CAPWAP tunnel
- Client keeps original IP and client’s data flows across the CAPWAP tunnel
What advantage do Mobility Groups provide and what 4 things are supported?
- Clients can roam quickly between controllers in the same Mobility Group.
- Layer 2 and Layer 3 roaming
- CCKM
- Key caching
- 802.11r credential caching.
What is true if a client roams between controllers not in the same mobility group?
Credentials are not cached and shared so clients must go through a full authentication during the roam.