Prasanna, If you reply to Cisco Support they could add this information to this 
document. This is really an issue with multiple WLC deployments with Fast 
Secure Roaming. The Cisco document is just defining Fast Secure Roaming 
requirement in general terms. I agree Cisco should update their document to 
show how a customer with a production environment is running with multiple WLCs 
with Fast Secure Roaming.

Some reference to document that Cisco does mention a WLC, Fast Secure Roaming 
in a multiple WLCs deployment:


URL:
http://www.cisco.com/en/US/docs/solutions/Enterprise/Mobility/vowlan/41dg/vowlandg.pdf

Fast Secure Roaming 
Fast roaming algorithms include Cisco Centralized Key Management (CCKM) and 
Proactive Key Caching (PKC). CCKM and PKC allow a WLAN client to roam to a new 
AP and re-establish a new session key-known as the Pairwise Transient Key 
(PTK)-between the client and AP without requiring a full IEEE 802.1X/EAP 
reauthentication to a AAA/RADIUS server. 
Both CCKM and PKC are Layer-2 roaming algorithms in that they to not consider 
any Layer-3 issues such address IP address changes. In the Cisco Unified 
Wireless Network, clients are allocated IP addresses from subnets that 
originate at the WLC-not the AP. In this way, it is possible to group large 
numbers of WLAN clients for a given SSID into the same Layer-2 subnet. This 
maximizes the scope of the Layer-2 domain-and the Fast Secure Roaming domain. 
Additionally, multiple-WLC deployments support client roaming across APs 
managed by WLCs in the same mobility group on the same or different subnets. 
This roaming is transparent to the client because the session is sustained and 
a tunnel between the WLCs allows the client to continue using the same 
DHCP-assigned or client-assigned IP address as long as the session remains 
active.

Regards,
Tracy Sutton
Fujitsu America Inc.
CCIE #37101

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of 
[email protected]
Sent: Tuesday, October 29, 2013 12:00 PM
To: [email protected]
Subject: CCIE_Wireless Digest, Vol 54, Issue 7

Send CCIE_Wireless mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://onlinestudylist.com/cgi-bin/mailman/listinfo/ccie_wireless
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific than "Re: 
Contents of CCIE_Wireless digest..."


Today's Topics:

   1. Best Practices for VoWLAN and Fast Roaming (Prasanna Yabaluri)


----------------------------------------------------------------------

Message: 1
Date: Tue, 29 Oct 2013 05:35:25 -0400
From: Prasanna Yabaluri <[email protected]>
To: "[email protected]"
        <[email protected]>
Subject: [OSL | CCIE_Wireless] Best Practices for VoWLAN and Fast
        Roaming
Message-ID:
        <CABwL-UPkM2AATfAJpeA+TD_=ahhf8m1dolqqbyh3-aqlczf...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Below document outlines basic guidelines for VoWLAN to work well...

https://supportforums.cisco.com/docs/DOC-26863

For Fast Roaming to happen not sure why no mention on WLCs being in same 
MOBILITY groups with same Virtual IP address. Also how about WLCs being in same 
RF group?

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
</archives/ccie_wireless/attachments/20131029/801aca20/attachment-0001.html>

------------------------------

_______________________________________________
CCIE_Wireless mailing list
[email protected]
http://onlinestudylist.com/cgi-bin/mailman/listinfo/ccie_wireless


End of CCIE_Wireless Digest, Vol 54, Issue 7
********************************************
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Reply via email to