From: Fabrice Bobes (study@6colabs.com)
Date: Tue Oct 22 2002 - 19:23:41 GMT-3
Actually I did this test with another vlan becoming the native vlan and
vlan1 down.
No luck, the vtp advertisements were not going through anymore.
Don't worry, I am incorrect almost all the time.
Fabrice
-----Original Message-----
From: Jay [mailto:ccienxtyear@hotmail.com]
Sent: Tuesday, October 22, 2002 2:41 PM
To: Fabrice Bobes
Subject: Re: VTP domain.
Sure is getting intereseting...and I am not syaing I am correct and you
are incorrect. I guess what I was trying to understand is if you shut
vlan 1 down and create another vlan which becomes your native vlan, how
is the vtp advertisements carried then ?
-Jay
----- Original Message -----
From: "Fabrice Bobes" <study@6colabs.com>
To: "'Jay'" <ccienxtyear@hotmail.com>
Sent: Saturday, October 19, 2002 4:44 PM
Subject: RE: VTP domain.
> This VTP thread is getting more interesting.
> Yes, the VTP messages are sent to destination mac 01-00-0c-cc-cc ...
> but they are only carried over VLAN1. It's not antinomic.
> The Trunk encapsulation doesn't matter.
>
> Fabrice
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of Jay
> Sent: Saturday, October 19, 2002 4:05 PM
> To: Fabrice Bobes; 'enginedrive2002'; ccielab@groupstudy.com
> Subject: Re: VTP domain.
>
>
> But..how is this possible...if you shut vlan 1 down and use another
> vlan as your native vlan...assuming you are talking about the 3550.
> VTP messages are sent either as ISL or dot1q frames across the Trunk
> to destination mac 01-00-0c-cc-cc-cc . The client switch listens for
> vtp messages sent to this mac address and this is how they learn what
> domain, vlans they need and configure themselves.
>
> -Jay
>
> ----- Original Message -----
> From: "Fabrice Bobes" <study@6colabs.com>
> To: "'enginedrive2002'" <enginedrive2002@yahoo.ca>;
> <ccielab@groupstudy.com>
> Sent: Saturday, October 19, 2002 2:54 PM
> Subject: RE: VTP domain.
>
>
> > This is correct, VTP is only carried over VLAN1. Obviously, you
> > can't disable VLAN1 from the trunk when using vtp.
> >
> > Fabrice
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> > Of enginedrive2002
> > Sent: Saturday, October 19, 2002 2:16 PM
> > To: ccielab@groupstudy.com
> > Subject: Re: VTP domain.
> >
> >
> > Thanks for the confirmation Fabrice and Stefan!
> >
> > I have another question about VTP: which vlan is used to
> > transmit/receive VTP packets? I remember read from somewhere that it
> > only use vlan1, is this true?
> >
> > Thanks!
> >
> >
> > E.D.
> >
> > ----- Original Message -----
> > From: "Stefan L. Dozier" <doziersl@yahoo.com>
> > To: "Fabrice Bobes" <study@6colabs.com>; <ccielab@groupstudy.com>
> > Sent: October 19, 2002 3:48 PM
> > Subject: RE: VTP domain.
> >
> >
> > > Ok...I've completed testing and I concur with your assessment and
> > > your
> >
> > > answer, that "vtp domain <domain name> on a configured client is
> > > "not"
> >
> > > a must!
> > >
> > > Given the situation, where the client switch is in a default vtp
> > > state, and it's vtp mode has been set to "client", you can connect
> > > him
> >
> > > to a vtp server via a trunk link, and have him "inherit" the vtp
> > > server's domain name.
> > >
> > > Good catch...I didn't know that, but I do now :-)
> > >
> > > Thanks for testing and increasing my level of knowledge! I've
> > > always
>
> > > set the domain name manually as well as ensure the client was
> > > actually
> >
> > > a vtp client, before connecting them to the network, less you'll
> > > possibly be struggling to bring your network back from death due
> > > to erasure of your vtp domain. :-)
> > >
> > > Stefan
> > >
> > >
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On
> > > Behalf Of
> >
> > > Fabrice Bobes
> > > Sent: Saturday, October 19, 2002 2:39 PM
> > > To: 'Stefan L. Dozier'; ccielab@groupstudy.com
> > > Subject: RE: VTP domain.
> > >
> > >
> > > Stefan,
> > >
> > > I can confirm that a vtp client in a default vtp state will get
> > > the vtp server's domain name via a trunk. I tried this on 2 of my
> > > Catalysts 3550 not later than yesterday. No, I wasn't bored.
> > >
> > > Thanks for the comments,
> > >
> > > Fabrice
> > >
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
> > > Behalf
>
> > > Of Stefan L. Dozier
> > > Sent: Saturday, October 19, 2002 11:07 AM
> > > To: ccielab@groupstudy.com
> > > Subject: RE: VTP domain.
> > >
> > >
> > > Comments Inline.....
> > >
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On
> > > Behalf Of
> >
> > > Fabrice Bobes
> > > Sent: Saturday, October 19, 2002 1:07 PM
> > > To: 'Stefan L. Dozier'; ccielab@groupstudy.com;
> > > enginedrive2002@yahoo.ca
> > > Subject: RE: VTP domain.
> > >
> > >
> > > OK, you can issue the "vtp domain" command on a switch in the
> > > client
>
> > > mode. But the switch will inherits the domain name via the trunk
> > > link.
> > >
> > > SLD> Maybe it will, I've never seen it happen, but I'll assume
> > > SLD> until
> > > I can test to be sure, that you're talking a switch with
> > > default vtp
> > > parameters, connected via trunk to a vtp server, and changed
> > > to a client, will pickup the vtp server's domain name.
> > > But if the client switch is not a default vtp state, i.e.
> > > vtp parameters have been previously configured, and you
change
> > > the domain name on the server, that domain name will not
> > propogate
> > > via vtp to the client switch, but will result in a vtp
mismatch
> > > as noted below.
> > >
> > > A vtp advertisement includes the VTP domain name.
> > >
> > > SLD> On this point, I stand corrected, the domain name is indeed
> > > included in the vtp advertisement. Which is why I'll
entertain
> > > the possibility above, until I can test and prove otherwise!
> > >
> > >
> > > The initial question is: Is the command "vtp domain" a must on a
> > > vtp
>
> > > client? My answer is you don't need it but you can enter it. You
> > > will learn the vtp domain name via the trunk.
> > >
> > > SLD> I'll save the debate here, until I can complete testing...
> > >
> > > If you enter the vtp domain on a vtp client you add some kind of
> > > security since the vtp advertisements will be ignored if the vtp
> > > domain mismatch.
> > >
> > > SLD> Well, I wouldn't call it a security mechanism, although
> > > SLD> you're
> > > right about the vtp adverts in the case of a vtp mismatch.
> > >
> > >
> > > Stefan
> > >
> > >
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
> > > Behalf
>
> > > Of Stefan L. Dozier
> > > Sent: Saturday, October 19, 2002 9:22 AM
> > > To: enginedrive2002; ccielab@groupstudy.com
> > > Subject: RE: VTP domain.
> > >
> > >
> > > Yes!
> > >
> > > I don't know of any other way to tell the "vtp client" the domain
> > > name
> >
> > > of your "vtp server" unless you issue the command "vtp domain
> > > <domain
> > > name> on the vtp client. It's not automagically transmitted via
> > > name> vtp
> > > advertisements if that's your line of thinking!
> > >
> > > caveat...
> > >
> > > "This assumes that you have 2 switches, one a vtp server and the
> > > other
> >
> > > a vtp client, and you want both switches in the same vtp domain"
> > >
> > > HTH
> > >
> > > Stefan
> > >
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On
> > > Behalf Of
> >
> > > enginedrive2002
> > > Sent: Saturday, October 19, 2002 11:43 AM
> > > To: ccielab@groupstudy.com
> > > Subject: VTP domain.
> > >
> > >
> > > Is the command "vtp domain <domain name>" a must on a VTP client
> > > when I already have VTP server configured?
> > >
> > > Thank you!
> > >
> > >
> > > E.D.
> >
> > ____________________________________________________________________
> > __
> > Post your free ad now! http://personals.yahoo.ca
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:54 GMT-3