That sounds correct, but I haven't had a chance to work with the Cisco wireless controller architecture much yet.<br><br><div class="gmail_quote">On Tue, Dec 9, 2008 at 11:59 AM, Jason Aarons (US) <span dir="ltr"><<a href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">I'm seeing Cisco Advanced Services set the access layer
3750s to trunking but the native vlan is routed and wireless vlan trunked.
The CUWN/LWAP access point vlan is the only thing going out to all access layer
3750s from distribution 6500s. I assume this allows fast secure wireless
roaming.</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">In short each closet has its own data/voice vlans, but a common
vlan across all switches for 1252 Access Points.</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;">
<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On
Behalf Of </b>Ben Story<br>
<b>Sent:</b> Tuesday, December 09, 2008 11:21 AM<br>
<b>To:</b> Dane<br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] Voice VLANs and Multiple Switches ?</span></p>
</div><div><div></div><div class="Wj3C7c">
<p> </p>
<p style="margin-bottom: 12pt;">You are correct in your notion
that Cisco recommends a best practice to not span VLANs between multiple
switches (unless those switches are acting a stackwise stack like the 3750 or
3750-E). I believe you can find this recommendation in the Campus Network
for High Availability SRND at <a href="http://www.cisco.com/en/US/docs/solutions/Enterprise/Campus/HA_campus_DG/hacampusdg.html" target="_blank">http://www.cisco.com/en/US/docs/solutions/Enterprise/Campus/HA_campus_DG/hacampusdg.html</a>
amid the Spanning Tree recommendations.</p>
<div>
<p>On Tue, Dec 9, 2008 at 10:16 AM, Dane <<a href="mailto:dane@pktloss.net" target="_blank">dane@pktloss.net</a>> wrote:</p>
<p>Someone correct me if I am wrong please, but I have always
been under<br>
the perception that when it comes to voice vlans (actually any vlan<br>
really) that Cisco recommends as a best practice to keep vlans from<br>
spanning multiple switches?<br>
<br>
For instance, say you have a building with four access switches<br>
dispersed throughout. Isn't the best practice to maintain a seperate<br>
voice and data vlan per access switch? So I should four data and four<br>
voice vlans in this example.<br>
<br>
Simply looking to determine if it is in fact Cisco best practice.<br>
Anyone happen to have anything from Cisco to confirm or deny this?<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></p>
</div>
<p style="margin-bottom: 12pt;"><br>
<br clear="all">
<br>
-- <br>
Ben Story CCSP, CCDA</p>
</div></div></div>
</div>
<div><p></p><hr size="1">
<p><b>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</b></p></div></blockquote></div><br><br clear="all"><br>-- <br>Ben Story CCSP, CCDA<br><br>