From: P729 (p729@cox.net)
Date: Sun Mar 09 2003 - 14:19:46 GMT-3
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 archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:35 GMT-3