From: jan vdb (jvdbro@yahoo.com)
Date: Sat Sep 30 2006 - 10:04:05 ART
Hello,
I think both methods are OK.
Forced or dynamic trunk, it won't matter as long as it is a trunk.
This is an example of a live VOIP network where we configured it via "forced" trunks!!
Example
interface GigabitEthernet1/0/1
switchport trunk encapsulation dot1q (Trunking encap method)
switchport trunk native vlan 37 (Your data Vlan as native (when port stop to trunk)
switchport trunk allowed vlan 37,64 (Vlan's allowed on your trunk)
switchport mode trunk (Forced the port to TRUNK)
switchport voice vlan 64 (Your VOICE Vlan => No need for Dot1p)
srr-queue bandwidth share 10 10 60 20 (Cat4k Q'ing)
srr-queue bandwidth shape 10 0 0 0
queue-set 2
priority-queue out
no snmp trap link-status
mls qos trust device cisco-phone
mls qos trust cos
no mdix auto
auto qos voip cisco-phone
spanning-tree portfast trunk
First method is also OK since the port is by default dynamic desirable and it will be negotiated to trunk via the switch in the IP-Phone.
You only need dot1p if you phone uses Dot1p priority tags.
switchport voive vlan dot1p (Packets are transported in vlan0).
Regards,
Jan
Radoslav Vasilev <deckland@gmail.com> wrote:
Hi,
The second one is incorrect.
The Voice VLAN feature can be configured on static access or dynamic
access ports.
Therefor configuring the port as dot1q is an incorrect. Now, once we
agree that the physical swtich port should be in access mode, we have
the following options for the additional voice vlan:
1. make the phone and the switch port carry the voice vlan in dot1q
frames (you don't need to configure the port as trunk !!!):
switchport voice vlan
don't forget to create the vlan on the vtp server/locally.
check the status with: show interface ... switchport
2. make the phone and the switch carry the voice vlan in dot1p frames
(traffic is CoS marked but uses the default vlan 0).
switchport voice vlan dot1p
check the status with: show interface ... switchport
Rado
On 9/30/06, Magmax wrote:
> Guys,
>
>
>
>
>
> Let say I am configuring voice port on 3550.Is there any difference in these
> two methods. In think both should be ok .
>
>
>
> Method 1
>
> mls qos
>
> interface FastEthernet0/19
>
> switchport access vlan XX
>
> switchport voice vlan XX
>
>
>
>
>
> Final config
>
>
>
>
>
> mls qos
>
> interface FastEthernet0/19
>
> switchport access vlan XX
>
> switchport voice vlan XX
>
> switchport mode dynamic desirable
>
> spanning-tree portfast
>
>
>
>
>
>
>
> Method 2
>
>
>
> mls qos
>
> interface FastEthernet0/7
>
> switchport voice vlan XX
>
> switchport trunk encapsulation dot1q
>
> switchport mode trunk
>
> switchport trunk native vlan XX
>
> mls qos trust cos
>
>
>
>
>
> Final config
>
>
>
> mls qos
>
> interface FastEthernet0/7
>
> switchport voice vlan XX
>
> switchport trunk encapsulation dot1q
>
> switchport mode trunk
>
> switchport trunk native vlan XX
>
> mls qos trust cos
>
> spanning-tree portfast
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Oct 01 2006 - 16:55:41 ART