Client w/higher revision number and server w/lower revision number

Unanswered Question
Apr 30th, 2010

Hello,

I read that when a client switch in VTP is powered up it sends a summary advertisement from its own stored database and if a server switch with a lower revision number is connected to the client switch it will accept the advertisement as a more up-to-date information.

I tryed the following in my lab: I unppluged the trunk between client and server.The client switch has revision number 4. I reseted the revision number of the server switch to 0. Both have the same domain name and VTP password. I turned the client switch off. Connected the trunk (cable) between client and server. Turned client switch on....... the revision number in the server is still 0.... whay is it not getting the advertisement from the client and updates its database to revision number 4 (in this case)? Any light on the subject?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
Loading.
Federico Coto F... Fri, 04/30/2010 - 09:30

Hi,

You say both have the same VTP domain/password.

The server indeed should synch to the client with higher revision number.

What's the status of the ''sh vtp status"?

VTP only travels on trunk links, make sure the connection between them is trunk.

Advertisements by default are every 5 minutes (unless there's a change which should happen immediatly)

Federico.

Edison Ortiz Fri, 04/30/2010 - 09:44

It works for me

Rack1SW4#sh vtp st
VTP Version                     : running VTP1 (VTP2 capable)
Configuration Revision          : 3
Maximum VLANs supported locally : 1005
Number of existing VLANs        : 10
VTP Operating Mode              : Client
VTP Domain Name                 : CISCO


Rack1SW3#sh vtp st
VTP Version                     : running VTP1 (VTP2 capable)
Configuration Revision          : 1
Maximum VLANs supported locally : 1005
Number of existing VLANs        : 8
VTP Operating Mode              : Server
VTP Domain Name                 : CISCO

Rack1SW3(config)#int f0/19
Rack1SW3(config-if)#no shut
Rack1SW3(config-if)#end
Rack1SW3#
*May 10 11:43:46.220: %SYS-5-CONFIG_I: Configured from console by console
*May 10 11:43:47.540: %LINK-3-UPDOWN: Interface FastEthernet0/19, changed state to down
*May 10 11:43:49.952: %LINK-3-UPDOWN: Interface FastEthernet0/19, changed state to up
Rack1SW3#
*May 10 11:43:51.968: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/19, changed state to up
Rack1SW3#sh vtp st
VTP Version                     : running VTP1 (VTP2 capable)
Configuration Revision          : 3
Maximum VLANs supported locally : 1005
Number of existing VLANs        : 10
VTP Operating Mode              : Server


Vlans that were created on SW4 prior changing to Client mode

Rack1SW4#
*May 10 11:43:03.756: %SYS-5-CONFIG_I: Configured from console by consolesh vlan

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Fa0/1, Fa0/2, Fa0/3, Fa0/4
                                                Fa0/5, Fa0/6, Fa0/7, Fa0/8
                                                Fa0/9, Fa0/10, Fa0/11, Fa0/12
                                                Fa0/13, Fa0/14, Fa0/15, Fa0/16
                                                Fa0/17, Fa0/18, Fa0/19, Fa0/20
                                                Fa0/21, Fa0/22, Fa0/23, Fa0/24
                                                Gi0/1, Gi0/2
10   VLAN0010                         active   
25   VLAN0025                         active   
50   VLAN0050                         active   
99   VLAN0099                         active   
100  VLAN0100                         active

Now SW3 has them


Rack1SW3#sh vlan

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Fa0/1, Fa0/2, Fa0/3, Fa0/4
                                                Fa0/5, Fa0/6, Fa0/7, Fa0/8
                                                Fa0/9, Fa0/10, Fa0/11, Fa0/12
                                                Fa0/13, Fa0/14, Fa0/15, Fa0/16
                                                Fa0/17, Fa0/18, Fa0/20, Fa0/21
                                                Fa0/22, Fa0/23, Fa0/24, Gi0/1
                                                Gi0/2
10   VLAN0010                         active   
25   VLAN0025                         active   
50   VLAN0050                         active   
99   VLAN0099                         active   
100  VLAN0100                         active  

fjcardenas-1 Fri, 04/30/2010 - 12:25

Not working for me:

SW-HC#show vtp status
VTP Version                     : 2
Configuration Revision          : 4
Maximum VLANs supported locally : 128
Number of existing VLANs        : 6
VTP Operating Mode              : Client
VTP Domain Name                 : SOFIA
VTP Pruning Mode                : Enabled
VTP V2 Mode                     : Enabled

SW-HC(config)#int fa 0/8
SW-HC(config-if)#shutdown

SW-REMOTO#show vtp status
VTP Version                     : 2
Configuration Revision          : 1
Maximum VLANs supported locally : 128
Number of existing VLANs        : 7
VTP Operating Mode              : Server
VTP Domain Name                 : SOFIA
VTP Pruning Mode                : Enabled
VTP V2 Mode                     : Enabled

SW-HC(config)#int fa 0/8
SW-HC(config-if)#no shutdown
SW-HC(config-if)#
03:20:26: %LINK-3-UPDOWN: Interface FastEthernet0/8, changed state to up
SW-HC(config-if)#
03:20:30: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed state to up

SW-REMOTO#show vtp status
VTP Version                     : 2
Configuration Revision          : 1
Maximum VLANs supported locally : 128
Number of existing VLANs        : 7
VTP Operating Mode              : Server
VTP Domain Name                 : SOFIA
VTP Pruning Mode                : Enabled
VTP V2 Mode                     : Enabled

SW-REMOTO#show interfaces fa 0/8 trunk

Port        Mode         Encapsulation  Status        Native vlan
Fa0/8       desirable    802.1q         trunking      1

Port      Vlans allowed on trunk
Fa0/8       1-4094

Port        Vlans allowed and active in management domain
Fa0/8       1-3

Port        Vlans in spanning tree forwarding state and not pruned
Fa0/8       1-2

I don't know why is not working for me.

Edison Ortiz Fri, 04/30/2010 - 12:30

Not sure why it does not work for you. It's a very straightforward process.. One thing is to be sure the VTP Domain name actually matches. Spaces after typing the VTP Domain name do count.

fjcardenas-1 Fri, 04/30/2010 - 13:19

It works now. I had my default-gateway in my client switch in a different subnet... I guess that's what it was because now it works. Thanks.

mlund Mon, 05/03/2010 - 01:19

Hi

A client switch will always populate it's learned vtp database to other switches when they come online, as long as they have lower revision number.

However, the client switch do not store the database, so if you turn the power off, the switch starts with an empty database when it's online again. Then it have to rely on other switches to send there vtp info to them.

The difference is with vtp server, because they store the database, and when they come online, they already have a database with the stored vlan's and revisionnumber to start with. 

/Mikael

Edison Ortiz Tue, 05/04/2010 - 08:30

However, the client switch do not store the database, so if you turn the power off, the switch starts with an empty database when it's online again.

That's not correct. If that's the case, how a client would disrupt a current VTP environment if it comes with an empty Vlan database?

mlund Wed, 05/12/2010 - 05:10

Hi Edison

You are completely right about that. The client actually stores it's database, and in case of a new connection to a switch with lower revision number and the same vtp name, it will for shure, overwrite the database of the new switch.

/Mikael

Actions

This Discussion