From: Jeff K. (jeffbk@xxxxxxxxxxxxx)
Date: Fri Nov 30 2001 - 01:38:43 GMT-3
True, it is possible theoretically for a rogue switch to have a higher
revision number but that's why I always use a password with VTP. Even then,
you should control the trunk status on your ports so that a 'rogue' switch
doesn't just come up (i.e., 'set trunk off' if it isn't a trunk port). In
my opinion, it just makes more sense to let VTP push out your VLAN
information to your other switches vs. doing it all yourself. Plus, with
tools like VMPS you don't always have to telnet in to assign ports...
I guess there's always more than one way to get the same thing done,
though...
----- Original Message -----
From: "Hansang Bae" <hbae@nyc.rr.com>
To: <ccielab@groupstudy.com>
Sent: Thursday, November 29, 2001 5:35 PM
Subject: Re: VTP Server
> At 02:36 PM 11/29/2001 -0600, Jeff K. wrote:
> >You definitely want to use VTP in your enterprise. What if you have 20
> >VLANs over 20 switches -- it would be a real waste of time to enter all
that
> >information over and over. Besides, VTP is not that intensive,
especially
> >in a switched LAN environment...
>
>
> You have to assign the ports so you have to telnet to the switches
> anyway. Creating a VLAN is a one line affair right? The down side is
that
> a rogue switch can simply wipe away your VLAN database.
>
> Besides, you don't change VLANs every day in most environments.
>
> Too bad switches won't accept ssh/telnet.
>
> hsb
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:27 GMT-3