DTP VTP
DTP VTP
&
VTP - VLAN Trunking Protocol
Todd Lammle
CCNA
Routing & Switching Study Guide
SYBEX, A Wiley Brand
Introduction
Exercise on DTP
DTP
Review Questions
VLAN trunks formed using DTP may utilize either IEEE 802.1Q or Cisco
ISL trunking protocols.
DTP should not be confused with VTP, as they serve different purposes.
Result:
switchport mode dynamic auto Verification command:
Fa0/1 Fa0/1 SW#show int fa0/1 switchport
TRUNK TRUNK
ACCESS ACCESS
Static access: It means an access port that belongs to a single VLAN that doesn’t change (unless we configure a
different VLAN). There are also dynamic access ports in which a server automatically assigns the VLAN depending
on the MAC address of the connected device.
CNW CSE4541 DTP-VTP
switchport mode Setting Contd...
DTP negotiations mode: dynamic auto
Setting: A switchport in dynamic auto mode
Fa0/1 Fa0/1
will NOT actively try to form a trunk
switchport mode dynamic auto
with other Cisco switches.
switchport mode trunk
switchport mode dynamic desirable
Result:
Verification command:
Fa0/1 Fa0/1 SW#show int fa0/1 switchport
TRUNK TRUNK
Result:
Verification command:
Fa0/1 Fa0/1 SW#show int fa0/1 switchport
ACCESS ACCESS
Verification command:
Result:
Fa0/1 Fa0/1 SW#show int fa0/1 switchport
TRUNK ACCESS
TRUNK TRUNK
NOTE: DTP will not form a trunk with a router, PC etc. The switchport will be
in access mode.
CNW CSE4541 DTP-VTP
DTP Conclusive Points
In older switches, switchport mode dynamic desirable is the de-
fault administrative mode.
DTP frames are sent in VLAN 1 when using ISL, or in the native VLAN
when using 802.1Q (the default native VLAN is VLAN 1, however).
The basic goals of VTP are to manage all configured VLANs across a
switched internetwork and to maintain consistency throughout that net-
work.
VTP allows you to add, delete, and rename VLANs information that is
then propagated to all other switches in the VTP domain.
2. VTP Client
Cannot add/modify/delete VLANs.
Do not store the VLAN database in non-volatile RAM(NVRAM)
Will synchronize their VLAN database to the server with the highest revision number
in their VTP domain
Will advertise their VLAN database and forward VTP advertisements to other clients
over their trunk ports.
Does not participate in the VTP domain or share its VLAN database.
Maintains its own database in NVRAM. It can add/modify/delete VLANs of own, but
they won’t be advertised to other switches.
Will forward VTP advertisements that are in the same domain as it.
Switches in VTP transparent mode advertise VTP management domain information
as well as a configuration revision number and all known VLANs with any specific
parameters.
The whole purpose of transparent mode is to allow remote switches to receive the
VLAN database from a VTP Server configured switch through a switch that is not
participating in the same VLAN assignments.
SW1#config t
SW1(config)#vtp ?
domain Set the name of the VTP administrative domain
mode Configure VTP device mode
password Set the password for the VTP administrative domain
Version Set the administrative domain to VTP version
SW1(config)#vtp mode ?
client Set the device to client mode
server Set the device to server mode
transparent Set the device to transparent mode
SW1#config t
SW1(config)#vtp domain ITER
VTP Version capable : 1 to 2
VTP Version running : 1
VTP Domain Name : ITER
VTP Pruning Mode : Disabled
::::::::
Feature VLAN :
--------------------
VTP Operation Mode : Server
Maximum VLANS supported locally : 255
Number of existing VLANS : 5
Configuration Revision : 0
MD5 digest : 0x7D 0x5A 0xA6 0x0E 0x9A 0x72 0xA0 0x3A
0xF0 0x58 0x10 0x6C 0x9C 0x0F 0xA0 0xF7
SW1#
Feature VLAN :
--------------------
VTP Operation Mode : Server
Maximum VLANS supported locally : 255
Number of existing VLANS : 6
Configuration Revision : 1
MD5 digest : 0x7D 0x5A 0xA6 0x0E 0x9A 0x72 0xA0 0x3A
0xF0 0x58 0x10 0x6C 0x9C 0x0F 0xA0 0xF7
SW1#
Client: In client mode, switches receive information from VTP servers. Clients receive and forward
updates, so in this way, they behave like VTP servers.
Client can not create, change, or delete VLANs. Additionally, none of the ports on a client switch
can be added to a new VLAN before the VTP server notifies the client switch of the new VLAN and
the VLAN exists in the client’s VLAN database.
VLAN information sent from a VTP server isn’t stored in NVRAM of the client. It means that if the
switch is reset or reloaded, the VLAN information will be deleted.
So basically, a switch in VTP client mode will forward VTP summary advertisements and process
them. This switch will learn about but won’t save the VTP configuration in the running configuration,
and it won’t save it in NVRAM. Switches that are in VTP client mode will only learn about and pass
along VTP information.
VLANs with IDs greater than 1005 are called extended-range VLANs and
they’re not stored in the VLAN database.
The switch must be in VTP transparent mode when you create VLAN IDs
from 1006 to 4094.
VLAN IDs 1 and 1002 to 1005 are automatically created on all switches
and cant be removed.
S1#config t
S1#(config)#vtp mode server
Device mode already VTP SERVER.
S1(config)#vtp domain Lammle
Changing VTP domain name from null to Lammle
S1(config)#vtp password todd
Setting device VLAN database password to todd
S1(config)#do show vtp password
VTP Password: todd
VTP Pruning:
S1#sh int trunk Shows all VLANs that are allowed across a trunked link by default.
Check the output of the above command for VTP pruning is disabled by default.
Enable pruning: takes one command and it is enabled on entire switched network for the listed VLANs.
S1#config t
S1(config)#int f0/1
S1(config-if)#switchport trunk ?
S1(config-if)#switchport trunk pruning ?
S1(config-if)#switchport trunk pruning vlan 3-4
The valid VLANs that can be pruned are 2 to 1001. Extended-range VLANs (VLAN IDs 1006 to 4094) can’t
be pruned, and these pruning-ineligible VLANs can receive a flood of traffic.
Configure the above switched netwrok and check the vtp status at switch SW1.
Verify the VTP status at other switches and draw the conclusion.
Now, Change the VTP domain name, CSE, at Switch SW2 and create a new VLAN at switch SW1.
Verify the VTP status at switch SW2. Conclude whether SW2 receives the update VTP revision number from
SW1 or not. Justify the reason
Verify the VTP status at switch SW3 and draw the conclusion.
Try to create a VLAN at switch SW4 and draw the conclusion. Find a way to create VLAN at SW4.
Guidelines:
Check & verify the output on switches: Switch#sh vtp status
Switches in VTP server mode will share VLAN information. For that VTP domain names should be configured
same over the switches.
If all switches can be servers and they can still share VLAN information.
If the VTP mode is client for any switch, then a VTP client cannot create, delete, or change VLANs,
VTP clients only keep the VTP database in RAM, and that’s not saved to NVRAM.
To create a VLAN on a switch (VTP mode is client), it is required to make that switch in VTP server first.
VTP VLAN information with the highest revision number can be only receive on switches.
By default, VTP operates in version 1.
You can configure VTP version 2 if you want support for these features, which are not supported in version 1:
Token Ring support
Unrecognized Type-Length-Value (TLV) support
Version-Dependent Transparent Mode
Consistency Checks