VTP Protocol and Its Configuration

VTP Protocol and its configuration VTP Protocol (VLAN Trunk Protocol) are the role of Cisco private Protocol: from a control point (that is, the server in VTP) maintain the composition of working VTP domains such as adding, deleting, and renaming VLANs on the entire enterprise network: the same domain name must be connected through Trunk. There are three VTP operating modes for a group of switches: -- VTP message provided by server: including vlan id and name information learning VTP messages of the same domain name forwarding VTP messages of the same domain name can be added, deleted, changed VLAN -- client Mode) requesting VTP message to learn VTP messages of the same domain name to forward VTP messages of the same domain name cannot be added or deleted. Changing VLAN-Transparent mode (Transparent) VTP messages are not provided, VTP messages are not learned, and VTP messages are forwarded. You can add, delete, and change VLANs. VTP notifications take effect only locally. 1. Client announcement request-obtain VLAN information condition: Switch restart; VTP domain name change; vswitch receives the summary announcement of the configuration revision number; 2. Server announcement response -- send VLAN information Summary announcement: used to notify the adjacent switch of the current VTP domain name and configuration revision number; send a notice subset notice once every 300 seconds or when the configuration changes: Contains VLAN details Note: The VTP announcement is sent using the multicast address. The address is 01-00-0c-cc-cc-cc and can only be sent through the trunk port (Serial Port) VTP messages are transmitted through VLAN 1. VTP version 1 and version 1: a VTP transparent transmission switch. You must check whether the VTP version and domain name match each other before forwarding VTP messages. 2. version 2: when forwarding VTP information, do not check the version number and domain name related configuration commands: # switchport mode trunk -- "Global" to set the Trunk link # vtp domain name-"VLAN Database ", create a VTP domain # vtp mode server | client | transparent -- 2950 series configure VTP mode # vtp server | client | transparent -- 3640 series configure VTP mode # vtp password -- configure VTP password # vtp pruning -- configure VTP build # vtp version 2 -- 2950 configure VTP version # vtp v2-mode -- 3640 configure VTP version # show vtp status example extension diagram: specific configuration steps: [Switch A] A (config) # interface f0/10A (config-if) # switchport mode trunk -- set this port to serial port mode A (config-if) # no shutdownA (config-if) # exitA (config) # exitA # vlan database -- enter VLAN database A (vlan) # vlan 2 -- create vlan 2A (vlan) # vlan 3 -- create vlan 3A (vlan) # exitA # show vlan-switch -- check whether the created VLAN is successful A # vlan databaseA (vlan) # vtp domain name -- the domain name must be uniform A (vlan) # vtp server -- set the mode to serverA # show vtp status -- check The vtp status as optional: A # vlan databasA (vlan) # vtp pruning -- set the trim Mode A (vlan) # vtp v2-mode -- set vtp version A (vlan) # vtp password -- if a password is set, the vswitches in the same domain name must set the same password. [Switch B] B (config) # interface f0/11B (config-if) # switchport mode trunkB (config-if) # no shutdownB (config-if) # exitB (config) # interface f0/10B (config-if) # switchport mode trunkB (config-if) # no shutdownB (config-if) # exit B # vlan databseB (vlan) # vtp domain nameB (vlan) # vtp clientB (vlan) # exitB # show vlan-switch -- check whether vlan information is learned. [switch C] C (config) # interface f0/10C (config-if) # switchport mode trunkC (config-if) # no shutdownC (config-if) # exitC (config) # C # vlan databseC (vlan) # vtp domain nameC (vlan) # vtp clientC (vlan) # exitC # show vlan-switch -- check whether vlan information is learned