Re: VTP (V2)

From: Divin Mathew John <divinjohn_at_gmail.com>
Date: Thu, 30 Apr 2009 18:17:45 +0530

Ali,

VTP Server and VTP client is just a VTP mode . In the server mode u
have the capability to create edit and delete Vlans. where as in
client mode you cant create delete or edi vlans. It tells nothing
about Server not accepting client's vlan config with a higher revsion
number.
 This is from the Cisco Doc Cd
VTP Modes

You can configure a switch to operate in any one of these VTP modes:

    *

      ServerIn VTP server mode, you can create, modify, and delete
VLANs and specify other configuration parameters, such as VTP version
and VTP pruning, for the entire VTP domain. VTP servers advertise
their VLAN configuration to other switches in the same VTP domain and
synchronize their VLAN configuration with other switches based on
advertisements received over trunk links. VTP server is the default
mode.
    *

      ClientVTP clients behave the same way as VTP servers, but you
cannot create, change, or delete VLANs on a VTP client.
    *

      TransparentVTP transparent switches do not participate in VTP.
A VTP transparent switch does not advertise its VLAN configuration and
does not synchronize its VLAN configuration based on received
advertisements, but transparent switches do forward VTP advertisements
that they receive out their trunk ports in VTP Version 2.
    *

      Off (configurable only in CatOS switches)In the three described
modes, VTP advertisements are received and transmitted as soon as the
switch enters the management domain state. In the VTP off mode,
switches behave the same as in VTP transparent mode with the exception
that VTP advertisements are not forwarded.

http://www.cisco.com/en/US/tech/tk389/tk689/technologies_tech_note09186a0080094c52.shtml#vtp_modes.

The configuration revision number of the switch that you inserted was
higher than the configuration revision number of the VTP domain.
Therefore, your recently introduced switch, with almost no configured
VLANs, erased all VLANs through the VTP domain.

This occurs whether the switch is a VTP client or a VTP server. A VTP
client can erase VLAN information on a VTP server. You can tell that
this has occurred when many of the ports in your network go into
inactive state but continue to be assigned to a nonexistent VLAN.

http://www.dide3d.com/2009/02/how-a-recently-inserted-switch-can-cause-network-problems/
http://www.cisco.com/en/US/tech/tk389/tk689/technologies_tech_note09186a0080890613.shtml#topic7

Thats how things work in VTPv1 and VTPv2.. Hence there is VTPv3 which
kinda fixes the higher revision number issue.
Thanking You

Yours Sincerely

Divin Mathew John
divinjohn_at_gmail.com
divin_at_dide3d.com
http://www.dide3d.com
+91 9945430983
+91 9846697191
+974 5008916
PGP PUBLIC KEY BLOCK @ http://www.dide3d.com/divin_Public_PGP_key.txt
Sent from Bangalore, KA, India

On Thu, Apr 30, 2009 at 3:06 PM, <ali_akbar99_at_yahoo.com> wrote:
> Hi All Experts,
>
> I have a small question regarding VTP (V2).
>
> I am bit confused why VTP client configuration revision number (Higher than the
> server) effects and change the VLAN configuration of server.
>
> As VTP transparent ignore all the update information from server or client than
> why not Server can ignore the higher configuration revision number if it is
> receiving from clients within a same domain.
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Thu Apr 30 2009 - 18:17:45 ART

This archive was generated by hypermail 2.2.0 : Mon May 04 2009 - 07:39:13 ART