VTP server and extended-range VLANs.

[speculor_cisco]

If a switch running VTP v2 boots with VTP server mode in the vlan.dat and VTP transparent mode in the startup-config and in the startup-config are configured some extended-range VLANs, is it possible to have a VTP server with extended-range VLANs configured?

Thanks.

[Peter Paluch]

Hi,

As far as I remember, the CCIE Routing&Switching Written Exam Certification Guide suggested that whenever the vlan.dat and the startup-config disagree, the vlan.dat is preferred. That would mean that the switch would boot with the vlan.dat file loaded and would reject all extended VLANs currently stored in the startup-config file.

Best regards,

Peter

[speculor_cisco]

Hello Peter and thanks for your answer.

From "Managing vlan.dat in Catalysts running IOS" Document 109304 you can read:

"If both the VLAN database and the configuration file show the VTP mode as transparent and the VTP

domain names match, the VLAN database is ignored. The VTP and VLAN configurations in the

startup configuration file are used. The VLAN database revision number remains unchanged in the

VLAN database."

"If the startup VTP mode is server mode, or the startup VTP mode or domain names do not match the

VLAN database, VTP mode and VLAN configuration for the first 1005 VLANs are selected by

VLAN database information, such as the vlan.dat file. VLANs greater than 1005 are configured from

the switch configuration file."

I have understood that there is a lot of confusion about this topic.

For me the startup VTP mode is server mode when startup-config does not indicate any VTP mode.

Do you know if it is possible to have startup-config with VTP mode server or client explicitely indicated?

If I am right, I can not imagine an example where some VLANs are configured from VLAN database and other

from startup-config without having VTP server mode.

Whay do you think about?