<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><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.</P><P>Regards,<BR></P><P></P><P>Mike J</P><BR>--- On <B>Sat, 3/14/09, Dane <I><dane@pktloss.net></I></B> wrote:<BR><BLOCKQUOTE style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">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<BR><BR><PRE>I can't speak for why the phone mac shows in both VLANs but I can
second what Lelio stated regarding moving voice out of VLAN 1. If
your going to move anything to a different VLAN your going to want to
move voice. Neither should be in VLAN 1 but if your going to leave
something in VLAN 1 its my understanding that separating out your
voice traffic would be the best idea. No expert though so I might be
wrong.
On Thu, Mar 12, 2009 at 1:31 PM, STEVEN CASPER <SCASPER@mtb.com> wrote:
> We have taken over a group of sites that have both the PCs and Cisco
phones
> in VLAN 1. I know this is not a good idea. As part of our conversion one
> option being looked at is temporarily moving the data to a new VLAN 50 and
> leaving the phones in VLAN 1. Testing this I see the phone is now in both
> VLANs. The phone and PC seem to be working fine still I think that this
may
> not be a valid config option and I am feeling very leery about this
> option. Opinions would be welcome. Here is what I got:
>
> interface FastEthernet0/19
> switchport access vlan 50
> switchport voice vlan 1
> spanning-tree portfast
>
> Vlan Mac Address Type Ports
> ---- ----------- -------- -----
> 1 001f.6c80.a7a5 DYNAMIC Fa0/19
> 50 001f.6c80.a7a5 DYNAMIC Fa0/19
>
>
>
> Please consider the impact on our environment before printing this e-mail.
>
> ************************************
> This email may contain privileged and/or confidential information that is
> intended solely for the use of the addressee. If you are not the intended
> recipient or entity, you are strictly prohibited from disclosing, copying,
> distributing or using any of the information contained in the
transmission.
> If you received this communication in error, please contact the sender
> immediately and destroy the material in its entirety, whether electronic
or
> hard copy. This communication may contain nonpublic personal information
> about consumers subject to the restrictions of the Gramm-Leach-Bliley Act
> and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or
> disclose such information for any purpose other than to provide the
services
> for which you are receiving the information.
> There are risks associated with the use of electronic transmission. The
> sender of this information does not control the method of transmittal or
> service providers and assumes no duty or obligation for the security,
> receipt, or third party interception of this transmission.
> ************************************
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
</PRE></BLOCKQUOTE></td></tr></table><br>