Here is the URL for Catalyst 3850 Technical Deep Dive presentation delivered during CiscoLive 2013 (London) where this product was announced.
Catalyst 3850 Technical Deep Dive
This session covered following technical topics in detail & you can get a understanding of how this platform architectures to do all of cool stuff introduced.
Update as of 7th March 2013
I got an opportunity to go for few Breakout sessions about this topic during CiscoLive Melbourne event. Those sessions are really informative & give you great insight of this new switch/controller platform & how we should design solutions with this new architecture. Here are the pdf of those presentations & I will post the link if recorded sessions available through Ciscolive365.
1. BRKEWN-2662 Converged Access Mobility Design & Architecture
2. BRKARC-2665 Converged Access Architecture Overview
3. BRKARC-2666 Converged Access Campus and Branch Design Guidance
Cisco recently set up private user group called my3850 where you can join & learn about this product platform.
mrn-cciew 
Hello Rasika,
Thank you for the collection of Cisco live material . I attended a 1 day work shop here in the UK but this was then relative new and I had not that many queries. The queries only then start when you a) start working with the solution b) have time and find interest looking at this or c) when you have the hardware handy to play with
I was wondering if you ever had to deal with the following – Converged access 3850 no WLC and Guest Wifi
I have been researching CCO and consulted various Cisco live presentations and concluded that this might not be best practice (or not yet documented) because I haven’t found anything relating to this query.
Basically, we are putting together a relatively small network (< 20 AP’s) utilizing the converged access solution with Catalyst 3850 but without a dedicated WLC for Guest WIFI. (ohh dear you might think, but please bear with me).
All services are hosted within the office. (a mini comms room data centre for that matter) and the project team has no further budged left to purchase a dedicated WLC to host Guest WIFI.
The idea is to terminate the Guest Wifi VLAN (layer 3) into a dedicated GUEST VRF which will be hosted on the collapsed core/distribution switch (also a 3850).
The access layer will be terminating the AP's and SSID and will be configured as Layer 2, effectively passing GUEST VLAN and CORP VLAN DATA VLAN ..and so forth via a trunk facing the core/dist switch.
I was wondering if anyone here has ever had to think of something similar or perhaps implemented a solution like this? If so , I would appreciate some guidance, input, or lesson learned.
PS: I appreciate that this approach might not be best practise yet but it would be useful if other options for small branch converged networks using Guest Wifi could be tested and published.
Attached is a high level draft of what we try to achieve. ( I try to attach a picture for your benefit)
Not sure if you have any thoughts on this.
Best Wishes
Markus
Hi Markus,
Unfortunately Guest Anchor feature is not supported by 3850. So you cannot tunnel all guest traffic to a single 3850 in a DMZ. Below is the 3.6E release note stating this.
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/3e/release_notes/OL3262101.html
HTH
Rasika
Hi Rasika,
Thank you for your help and reply and link. I did not know that.
I looked into other options and we are thinking to use our new firewall to terminate the guest traffic and place the guest WiFI into a VRF on the dist/core switch which connects to our external firewall.
> Access Switch 3850 MA
*) will have DATA, VOICE, COPR-WIFI and GUEST VLAN in data base
*) wll have a layer 3 for AP-MGMT svi and a loopback for management
> Dist/Core Switch 3850 (no MA or MC function no AP termination)
Will have all VLANS for DATA etc…and will have a GUEST SVI placed into a GUEST-VRF VRF IOS DHCP Server for Guest traffic
Or a layer 3 interface if SVI vRF is not supported yet.
Then the Dist/Core connects to the Firewall on a trunk configured part of the GUEST VRF Subnet and let the firewall break out and handle the policies
I know its not ideal but a small network for now and GUEST-WIFI authentication will be PSK based for now.
I know there are several ways when it comes to designing and implementing a network. Might be not suitable for large deployments thought
Feel free to comment but don’t worry if you don’t 🙂 as I know you are busy
Best wishes and thanks for your reply.
markusa