From: Donny MATEO (donny.mateo@sg.ca-indosuez.com)
Date: Sun Mar 09 2003 - 23:50:01 GMT-3
Then what of the COS value? The docCD on 3550 says that only ISL and dot1Q frame can contain COS value which they inserted in the header (for ISL) or on the tag in dot1Q. It did explicitly that any other kind of frame would carry no COS value and that
they will be assigned with the default port COS of 0 (unless specified otherwise).
Does this "auxilary VLAN" address this issue, so that the switch does not have of a trunk mode to recognize COS value in frame ?
Regards,
Donny
"P729"
<p729@cox.net> To: "Mahmud, Yasser" <YMahmud@Solutions.UK.ATT.com>
Sent by: cc: <ccielab@groupstudy.com>
nobody@groupstudy Subject: Re: 4p84: RE: voice vlans correct configuration
.com
10-03-2003 01:19
Please respond to
"P729"
It's a special case--a so-called "auxiliary VLAN." It supports the tag but
it doesn't carry the trunking protocols, etc. Certain switches with later
code can be configured to detect whether there is really a phone on the
other end before forming the aux VLAN to make it more difficult for someone
to emulate a trunk and abuse the trusted CoS.
Regards,
Mas Kato
https://ecardfile.com/id/mkato
----- Original Message -----
From: "Mahmud, Yasser" <YMahmud@Solutions.UK.ATT.com>
To: "'Scott Morris'" <swm@emanon.com>
Cc: <ccielab@groupstudy.com>
Sent: Sunday, March 09, 2003 7:43 AM
Subject: RE: 4p84: RE: voice vlans correct configuration
Scott,
If you use the the below config then does it mean the the connection b/w the
phone and the 3550 doesn't create a 802.1 trunk. How is it possible then for
the connection to support a vlan tag for voice traffic in
order to differentiate b/w voice and data traffic.
1.
mls qos
!
interface fastethernet 0/10
switchport mode access
switchport access vlan 10
switchport voice vlan 100
mls qos trust cos
Rgds,
Yasser
> -----Original Message-----
> From: Scott Morris [SMTP:swm@emanon.com]
> Sent: Wednesday, February 26, 2003 1:39 PM
> To: zhaozx@DigitalChina.com; 'Hunt Lee'
> Cc: ccielab@groupstudy.com
> Subject: RE: 4p84: RE: voice vlans correct configuration
>
> Voice VLANs are actually an access-port technology. They can be done
> with a trunk port as well, but if you do it that way, do you not think
> you'd need to turn off a lot of VLANs (extraneous ones) to that trunk?
> No sense sending EVERYTHING to your phone!
>
> Both are workable configurations. IMHO, the access-port method is the
> "more correct" one.
>
> Scott
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> zhaozx@DigitalChina.com
> Sent: Wednesday, February 26, 2003 1:22 AM
> To: Hunt Lee
> Cc: ccielab@groupstudy.com
> Subject: 4p84: RE: voice vlans correct configuration
>
>
> mls qos
> !
> interface fastethernet 0/10
> switchport mode trunk
> awitchport trunk native vlan 10
> switchport trunk encapsulation dot1q
> switchport voice vlan 100
> mls qos trust cos
>
>
> the 2nd one...
>
> Voice VLAN only works on a Trunk port ;-)
>
> Regards,
> Hunt
>
>
> -----Original Message-----
> From: Cezar Fistik [mailto:cfistik@moldovacc.md]
> Sent: Wednesday, 26 February 2003 12:57 PM
> To: ccielab@groupstudy.com
> Subject: voice vlans correct configuration
>
>
> Hi group,
>
> Could you please, share your ideas about the following configurations.
> Just assume that an ip phone is connected to int fast 0/10 and to the
> phone is connected a pc that is supposed to be in vlan 10
>
> 1.
> mls qos
> !
> interface fastethernet 0/10
> switchport mode access
> switchport access vlan 10
> switchport voice vlan 100
> mls qos trust cos
>
> 2.
> mls qos
> !
> interface fastethernet 0/10
> switchport mode trunk
> switchport trunk encapsulation dot1q
> switchport voice vlan 100
> mls qos trust cos
>
> Which one do you think is correct? Or if they are both incorect I'll
> appreciate any advice.
>
> Thanks,
> Cezar Fistik
This message is for information purposes only and its content
should not be construed as an offer, or solicitation of an offer,
to buy or sell any banking or financial instruments or services
and no representation or warranty is given in respect of its
accuracy, completeness or fairness. The material is subject
to change without notice. You should take your own independent
tax, legal and other professional advice in respect of the content
of this message. This message may contain confidential or
legally privileged material and may not be copied, redistributed
or published (in whole or in part) without our prior written consent.
This email may have been intercepted, partially destroyed,
arrive late, incomplete or contain viruses and no liability is
accepted by any member of the Credit Agricole Indosuez group
as a result. If you are not the intended recipient of this message,
please immediately notify the sender and delete this message
from your computer.
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:36 GMT-3