Re: configurin VOICE VLAN.

From: Matt White (mwhite23@gmail.com)
Date: Mon Mar 21 2005 - 23:47:09 GMT-3


I don't know what that is either, no such command as far as I can find.

Switch(config-if)#switchport p?
port-security priority protected

Switch(config-if)#switchport prio
Switch(config-if)#switchport priority ?
   extend Set appliance 802.1p priority

Switch(config-if)#switchport priority

"switchport priority extend trust" OR "switchport priority extend cos
0-7" either will trust or override/set the QoS parameters for the
computer attached to the other side of the phone. Typically you want
this set to zero (the default), although I have done some clever things
in the realm of daisychaining phones, polycom stuff, etc... with this
command.

On Mar 21, 2005, at 7:03 PM, Jongsoo.Kim@Intelsat.com wrote:

> Thanks for a good explanation Matt
>
> I remember I used to struggle a lot on this.
> I never thought about dynamic mode...
>
> One question though " switchport priority trust cos" on Method1 is
> necessary?
> First, I can't find this command from CCO. I only see "switchport
> priority
> extend ..."
> But as far as I know, this command("switchport priority extend ...")
> advise
> VoIP Phone on how to tag data traffic, which can also be used in
> method 2. I
> am just trying be 100% sure as my lab date is coming soon ( 5 April)
>
> Regards
>
> Jongsoo
>
> -----Original Message-----
> From: Matt White [mailto:mwhite23@gmail.com]
> Sent: Saturday, 19 March, 2005 11:16 PM
> To: mani poopal
> Cc: ccielab@groupstudy.com
> Subject: Re: configurin VOICE VLAN.
>
>
> For the 3550 and up, #1 is correct. #2 only needs to be used if you
> have a 3500XL or below.
>
> Keep in mind the switchport is dynamic by default, and will trunk
> automatically, regardless of the voice VLAN.
>
> Officially, #2 is wrong, as hardcoded trunks are not technically
> supported on an interface. However you see it implemented fairly often
> this way.
>
>
>
> On Mar 19, 2005, at 10:54 PM, mani poopal wrote:
>
>> Guys,
>>
>> If the question ask to configure voice vlan 200 and data vlan of 20,
>> which method is wright. Any suggesions are appreciated.
>>
>> Method1:(DOC CD and IWEB method)
>> mls qos
>> int fa 0/10
>> mls qos trust cos
>> switchport access vlan 20
>> switchport voice vlan 200
>> switchport priority trust cos
>>
>> Method2:(CISCO PRESS CCIE LAB EXAM book method)
>> mls qos
>> int fa 0/10
>> mls qos trust cos
>> switchport access-vlan 20
>> switchport voice-vlan 200
>> switchport trunk encapsulation dot1q
>> switchport moe trunk
>> switchport native vlan 20
>>
>> So the question, if the voice vlan is asked to configure, which method
>> is right.
>>
>> thanks in advance for the replies and reasoning.
>>
>> Mani
>>
>>
>>
>> ---------------------------------
>> Do you Yahoo!?
>> Yahoo! Small Business - Try our new resources site!
>>
>> ______________________________________________________________________
>> _
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> ############################################################
>
> Building on 40 Years of Leadership - As a global communications leader
> with 40 years of experience, Intelsat helps service providers,
> broadcasters, corporations and governments deliver information and
> entertainment anywhere in the world, instantly, securely and reliably.
>
> ############################################################
> This email message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged
> information. Any unauthorized review, use, disclosure or
> distribution is prohibited. If you are not the intended
> recipient, please contact the sender by reply email and
> destroy all copies of the original message. Any views
> expressed in this message are those of the individual
> sender, except where the sender specifically states them
> to be the views of Intelsat, Ltd. and its subsidiaries.
> ############################################################



This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:49 GMT-3