[c-nsp] VTP doubt

Nick Cutting ncutting at edgetg.com
Thu Jun 16 13:35:26 EDT 2016

If you must use VTP in production - use version 3 if you can, they got rid of the floors that cause the nightmare that Patrick mentioned.

Also remember that VTP and vlan broadcast domains are totally separate - VTP is just config replication.

-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Patrick M. Hausen
Sent: Thursday, June 16, 2016 1:25 PM
To: james list
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] VTP doubt


> Am 16.06.2016 um 18:52 schrieb james list <jameslist72 at gmail.com>:
> Hi
> I've two 6500 (6500-A and 6500-B) in production as VTP server, access 
> switch are 3750 or 4500 as VTP clients.
> Today if I add manually a vlan on one of the two VTP server (ie on 
> 6500-A) it's propagated to the other server (6500-B) and clients.
> The question is: do I've to add manually on both VTP servers or just 
> one is enough to keep redundancy ?

Only one. If both C6500 are in server mode they will synchronize and save the VTP data. You can check the status like this:

Core1#sh vtp status
VTP Version                     : 3 (capable)
Configuration Revision          : 199
Maximum VLANs supported locally : 1005
Number of existing VLANs        : 55
VTP Operating Mode              : Server

If the configuration revision on both servers is the same, they are in sync.
It doesn't matter on which you add the new VLAN.

> If VTP server (6500-A) is broken down for any reason, does 6500-B 
> still know the vlan added before only on 6500-B and continue to 
> propagate to clients ?

Yes, it will.

A popular way to shoot yourself in the foot is to bring a new system into your VTP domain that has been used before and has got:

* VTP server mode enabled
* VTP data with a revision higher than your exisiting equipment

Plug in for instant fun :-) Been there, ...

punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100
info at punkt.de       http://www.punkt.de
Gf: Jürgen Egeling      AG Mannheim 108285

cisco-nsp mailing list  cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list