[c-nsp] Data VLAN/Voice VLAN

[Bill Blackford]

If you are using 3560's, this has been my experience as well. If you are unfortunate enough to be using 3550XL's, then the whole game is different. 

The 3550XL way:

interface FastEthernet0/5
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 68
 switchport mode trunk
 switchport voice vlan 66
 switchport priority extend cos 0
 spanning-tree portfast

The data vlan has to be indicated as native.

Again, this has been my experience.

-b



-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Peter Rathlev
Sent: Friday, August 28, 2009 3:44 PM
To: Yuri Bank
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Data VLAN/Voice VLAN

On Fri, 2009-08-28 at 15:20 -0700, Yuri Bank wrote:
> interface FastEthernet0/4
>  description phone
>  switchport access vlan 77
>  switchport trunk native vlan 55
>  switchport mode access
>  switchport voice vlan 66
> 
> In this configuration, data is placed on vlan 55? From what I've read
> on other forums and such is that the data would be on the configured
> access vlan ( 77 ). Unfortunately I do not have an iphone to test
> this. Could anyone give me some clarity?

Untagged traffic on the port would be VLAN 77, since this is what you
configured at access VLAN and since the port is in forced access mode.

A compatible device (i.e. one the presents itself as a phone via CDP)
would activate the voice VLAN and thus allow tagged incoming traffic on
VLAN 66. This requires the switch (and port) to have CDP enabled by the
way.

The trunk configuration is ignored when you issue "switchport mode
access".

If you only need a stand-alone phone you can just use a simple access
port in the voice VLAN.

Regards,
Peter


_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/