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.<br>
<br><div class="gmail_quote">On Tue, Dec 9, 2008 at 10:16 AM, Dane <span dir="ltr"><<a href="mailto:dane@pktloss.net">dane@pktloss.net</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;">
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">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><br>
</blockquote></div><br><br clear="all"><br>-- <br>Ben Story CCSP, CCDA<br><br>