<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Due to special tagging involved, it is a REALLY bad idea to keep
voice traffic in VLAN 1. (If you have to keep something in VLAN 1, keep the
data traffic and move the voice to a different VLAN.) <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The following document describes Cisco’s thinking behind the
MVAP configuration – and also why the old trunk-based config is no longer
recommended by Cisco:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a
href="http://www.cisco.com/en/US/products/hw/switches/ps4324/products_configuration_example09186a0080722cdb.shtml">http://www.cisco.com/en/US/products/hw/switches/ps4324/products_configuration_example09186a0080722cdb.shtml</a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Here is the relevant excerpt:<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'>When you connect an IP phone to a switch using a trunk
link, it can cause high CPU utilization in the switches. As all the VLANs for a
particular interface are trunked to the phone, it increases the number of STP
instances the switch has to manage. This increases the CPU utilization.
Trunking also causes unnecessary broadcast / multicast / unknown unicast
traffic to hit the phone link.<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'>In order to avoid this, remove the trunk configuration and
keep the voice and access VLAN configured along with Quality of Service (QoS).
Technically, it is still a trunk, but it is called a Multi-VLAN Access Port
(MVAP). Because voice and data traffic can travel through the same port, you
should specify a different VLAN for each type of traffic. You can configure a
switch port to forward voice and data traffic on different VLANs. Configure IP
phone ports with a voice VLAN configuration. This configuration creates a
pseudo trunk, but does not require you to manually prune the unnecessary VLANs.<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'>The voice VLAN feature enables access ports to carry IP
voice traffic from an IP phone. The voice VLAN feature is disabled by default.
The Port Fast feature is automatically enabled when voice VLAN is configured.
When you disable voice VLAN, the Port Fast feature is not automatically
disabled. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Given that MVAP is a pseudo-trunk, it is normal to see the phone
in both VLANs – in fact, if you have a computer plugged into the phone,
you will see three entries per switch port: two for the phone (in both data and
voice VLANs) and one for the computer (in data VLAN only). <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>HTH,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Nikola<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>-------------------------------------------<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Nikola Stojsin<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>PhD CCIE #12888<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>President<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Network Makers LLC<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>110 Wall Street, 11th Floor<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>New York, NY 10005<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>(212) 709-8201<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>(212) 706-2986 (fax)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a href="mailto:nikolas@networkmakers.com"><span
style='color:#1F497D'>nikolas@networkmakers.com</span></a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>-------------------------------------------<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Mike Jones<br>
<b>Sent:</b> Sunday, March 15, 2009 10:41 PM<br>
<b>To:</b> STEVEN CASPER; Dane<br>
<b>Cc:</b> Cisco VOIP<br>
<b>Subject:</b> Re: [cisco-voip] Voice in VLAN 1<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0>
<tr>
<td valign=top style='padding:0in 0in 0in 0in'>
<p>I would recommend creating a data VLAN also and moving pcs/ data to that.
The phone will show in the data VLAN also due to the inbuilt switch and
the active PC connection on that VLAN, plugged into the phone.<o:p></o:p></p>
<p>Regards,<o:p></o:p></p>
<p>Mike J<o:p></o:p></p>
<p class=MsoNormal><br>
--- On <b>Sat, 3/14/09, Dane <i><dane@pktloss.net></i></b> wrote:<o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>From: Dane
<dane@pktloss.net><br>
Subject: Re: [cisco-voip] Voice in VLAN 1<br>
To: "STEVEN CASPER" <SCASPER@mtb.com><br>
Cc: "Cisco VOIP" <cisco-voip@puck.nether.net><br>
Date: Saturday, March 14, 2009, 10:00 PM<o:p></o:p></p>
<pre>I can't speak for why the phone mac shows in both VLANs but I can<o:p></o:p></pre><pre>second what Lelio stated regarding moving voice out of VLAN 1. If<o:p></o:p></pre><pre>your going to move anything to a different VLAN your going to want to<o:p></o:p></pre><pre>move voice. Neither should be in VLAN 1 but if your going to leave<o:p></o:p></pre><pre>something in VLAN 1 its my understanding that separating out your<o:p></o:p></pre><pre>voice traffic would be the best idea. No expert though so I might be<o:p></o:p></pre><pre>wrong.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>On Thu, Mar 12, 2009 at 1:31 PM, STEVEN CASPER <SCASPER@mtb.com> wrote:<o:p></o:p></pre><pre>> We have taken over a group of sites that have both the PCs and Cisco<o:p></o:p></pre><pre>phones<o:p></o:p></pre><pre>> in VLAN 1. I know this is not a good idea. As part of our conversion one<o:p></o:p></pre><pre>> option being looked at is temporarily moving the data to a new VLAN 50 and<o:p></o:p></pre><pre>> leaving the phones in VLAN 1. Testing this I see the phone is now in both<o:p></o:p></pre><pre>> VLANs. The phone and PC seem to be working fine still I think that this<o:p></o:p></pre><pre>may<o:p></o:p></pre><pre>> not be a valid config option and I am feeling very leery about this<o:p></o:p></pre><pre>> option. Opinions would be welcome. Here is what I got:<o:p></o:p></pre><pre>><o:p> </o:p></pre><pre>> interface FastEthernet0/19<o:p></o:p></pre><pre>> switchport access vlan 50<o:p></o:p></pre><pre>> switchport voice vlan 1<o:p></o:p></pre><pre>> spanning-tree portfast<o:p></o:p></pre><pre>><o:p> </o:p></pre><pre>> Vlan Mac Address Type Ports<o:p></o:p></pre><pre>> ---- ----------- -------- -----<o:p></o:p></pre><pre>> 1 001f.6c80.a7a5 DYNAMIC Fa0/19<o:p></o:p></pre><pre>> 50 001f.6c80.a7a5 DYNAMIC Fa0/19<o:p></o:p></pre><pre>><o:p> </o:p></pre><pre>><o:p> </o:p></pre><pre>><o:p> </o:p></pre><pre>> Please consider the impact on our environment before printing this e-mail.<o:p></o:p></pre><pre>><o:p> </o:p></pre><pre>> ************************************<o:p></o:p></pre><pre>> This email may contain privileged and/or confidential information that is<o:p></o:p></pre><pre>> intended solely for the use of the addressee. If you are not the intended<o:p></o:p></pre><pre>> recipient or entity, you are strictly prohibited from disclosing, copying,<o:p></o:p></pre><pre>> distributing or using any of the information contained in the<o:p></o:p></pre><pre>transmission.<o:p></o:p></pre><pre>> If you received this communication in error, please contact the sender<o:p></o:p></pre><pre>> immediately and destroy the material in its entirety, whether electronic<o:p></o:p></pre><pre>or<o:p></o:p></pre><pre>> hard copy. This communication may contain nonpublic personal information<o:p></o:p></pre><pre>> about consumers subject to the restrictions of the Gramm-Leach-Bliley Act<o:p></o:p></pre><pre>> and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or<o:p></o:p></pre><pre>> disclose such information for any purpose other than to provide the<o:p></o:p></pre><pre>services<o:p></o:p></pre><pre>> for which you are receiving the information.<o:p></o:p></pre><pre>> There are risks associated with the use of electronic transmission. The<o:p></o:p></pre><pre>> sender of this information does not control the method of transmittal or<o:p></o:p></pre><pre>> service providers and assumes no duty or obligation for the security,<o:p></o:p></pre><pre>> receipt, or third party interception of this transmission.<o:p></o:p></pre><pre>> ************************************<o:p></o:p></pre><pre>><o:p> </o:p></pre><pre>> _______________________________________________<o:p></o:p></pre><pre>> cisco-voip mailing list<o:p></o:p></pre><pre>> cisco-voip@puck.nether.net<o:p></o:p></pre><pre>> https://puck.nether.net/mailman/listinfo/cisco-voip<o:p></o:p></pre><pre>><o:p> </o:p></pre><pre>><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>cisco-voip mailing list<o:p></o:p></pre><pre>cisco-voip@puck.nether.net<o:p></o:p></pre><pre>https://puck.nether.net/mailman/listinfo/cisco-voip<o:p></o:p></pre></td>
</tr>
</table>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p>
</div>
</body>
</html>