RE: ΄πΈ΄: RE: voice vlans correct configuration

From: Scott M. Livingston (scottl@sprinthosting.net)
Date: Sun Mar 09 2003 - 19:00:35 GMT-3


Thats 2 of you now that sing the same song. Thank you!!!

scott

-----Original Message-----
From: Todd.Reagan@nokia.com [mailto:Todd.Reagan@nokia.com]
Sent: Sunday, March 09, 2003 3:56 PM
To: scottl@sprinthosting.net; YMahmud@Solutions.UK.ATT.com; p729@cox.net
Cc: ccielab@groupstudy.com
Subject: RE: 4p84: RE: voice vlans correct configuration

If you confgure a port on a 3550 "switch voice vlan 300" and vlan 300
does not exist, it will accept the command but you must add the vlan
manually after configuring the port for the voice vlan to work. It does
not automatically create the vlan like when you configure "switch access
vlan 300".
 
Hope this answers your question...
 
Todd
 

        -----Original Message-----
        From: ext Scott M. Livingston [mailto:scottl@sprinthosting.net]
        Sent: Sun 3/9/2003 3:36 PM
        To: 'Mahmud, Yasser'; 'P729'
        Cc: ccielab@groupstudy.com
        Subject: RE: 4p84: RE: voice vlans correct configuration
        
        

        One other thing about VV's (Voice Vlan's) I would like to ask.
I dont
        have Voice gear at the house so I have to ask this crazy
question. Do
        we need to actually create the VV on the vtp server or by just
adding
        the command 'switchport voice vlan x' under the interface take
care of
        everything for us?
        
        If I had to guess I would say we would not have to create it..
hhmmmm
        whatchya think?
        
        Thanks,
        scott
        
        -----Original Message-----
        From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
Behalf Of
        Mahmud, Yasser
        Sent: Sunday, March 09, 2003 11:40 AM
        To: 'P729'
        Cc: 'ccielab@groupstudy.com'
        Subject: RE: 4p84: RE: voice vlans correct configuration
        
        Mas,
        Thks for the explanation,
        
        One for more thing if we use auxiliary VLAN option then the
VLAN's
        allowed
        automatically are only the access vlan and voice vlan.
        Now if we use the dot1q method are the VLAN's allowed listed as
all ?? /
        or
        is it just the native and voice vlan ??(because of the
functionality of
        the
        switchport voice command)
        
        Thks
        
        Yasser
        
        
> -----Original Message-----
> From: P729 [SMTP:p729@cox.net]
> Sent: Sunday, March 09, 2003 5:20 PM
> To: Mahmud, Yasser
> Cc: ccielab@groupstudy.com
> Subject: Re: 4p84: RE: voice vlans correct configuration
>
> 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