-
Cisco IOS Switching Services Command Reference, Release 12.3
-
Introduction
-
Switching Commands: A through D
-
Switching Commands: enabled through ip flow ingress
-
Switching Commands: ip load-sharing through list
-
Switching Commands: mac-address-table aging-time through mpls ip encapsulate explicit-null
-
Switching Commands: mpls ip propagate-ttl through mpls request-labels for
-
Switching Commands: mpls traffic-eng through name server-atm-address
-
Switching Commands: neighbor activate through show cef timers
-
Switching Commands: show controllers vsi control-interface through show ip cache verbose flow
-
Switching Commands: show ip cef through show ip vrf
-
Switching Commands: show isis database verbose through show show mls rp vtp-domain
-
Switching Commands: show mpls atm-ldp bindings through show mpls traffic-eng link-management summary
-
Switching Commands: show mpls traffic-eng topology through show tag-switching tdp bindings
-
Switching Commands: show tag-switching tdp discovery through tag-switching tdp holdtime
-
Switching Commands: tunnel flow egress-records through vtp v2-mode
-
Table Of Contents
tunnel mpls traffic-eng affinity
tunnel mpls traffic-eng auto-bw
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng autoroute metric
tunnel mpls traffic-eng bandwidth
tunnel mpls traffic-eng load-share
tunnel mpls traffic-eng path-option
tunnel mpls traffic-eng priority
tunnel mpls traffic-eng record-route
vlan (VLAN configuration mode)
tunnel flow egress-records
To create a NetFlow record for packets that are encapsulated by a generic routing encapsulation (GRE) tunnel when both NetFlow and Cisco Express Forwarding (CEF) are enabled, use the tunnel flow egress-records command in interface configuration mode. To disable NetFlow record creation, use the no form of this command.
tunnel flow egress-records
no tunnel flow egress-records
Syntax Description
This command has no arguments or keywords.
Defaults
A NetFlow record for encapsulated packets is not created.
Command Modes
Interface configuration
Command History
Usage Guidelines
When this command is enabled on a GRE tunnel with both CEF and NetFlow enabled, a NetFlow record is created for packets that are encapsulated by the tunnel.
Examples
The following example shows how to enable NetFlow record creation:
Router(config-if)# tunnel flow egress-recordsRelated Commands
tunnel mode mpls traffic-eng
To set the mode of a tunnel to Multiprotocol Label Switching (MPLS) for traffic engineering, use the tunnel mode mpls traffic-eng command in interface configuration mode. To disable this feature, use the no form of this command.
tunnel mode mpls traffic-eng
no tunnel mode mpls traffic-eng
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command specifies that the tunnel interface is for an MPLS traffic engineering tunnel and enables the various tunnel MPLS configuration options.
Examples
The following example shows how to set the mode of the tunnel to MPLS traffic engineering:
Router(config-if)# tunnel mode mpls traffic-engRelated Commands
tunnel mpls traffic-eng affinity
To configure an affinity (the properties the tunnel requires in its links) for a Multiprotocol Label Switching (MPLS) traffic engineering tunnel, use the tunnel mpls traffic-eng affinity command in interface configuration mode. To disable the MPLS traffic engineering tunnel affinity, use the no form of this command.
tunnel mpls traffic-eng affinity properties [mask mask value]
no tunnel mpls traffic-eng affinity properties [mask mask value]
Syntax Description
Defaults
properties: 0X00000000
mask value: 0X0000FFFFCommand Modes
Interface configuration
Command History
Usage Guidelines
The affinity determines the attributes of the links that this tunnel will use (that is, the attributes for which the tunnel has an affinity). The attribute mask determines which link attribute the router should check. If a bit in the mask is 0, an attribute value of a link or that bit is irrelevant. If a bit in the mask is 1, the attribute value of a link and the required affinity of the tunnel for that bit must match.
A tunnel can use a link if the tunnel affinity equals the link attributes and the tunnel affinity mask.
Any properties set to 1 in the affinity should also be 1 in the mask. In other words, affinity and mask should be set as follows:
tunnel_affinity = (tunnel_affinity and tunnel_affinity_mask)Examples
The following example shows how to set the affinity of the tunnel to 0x0101 mask 0x303:
Router(config-if)# tunnel mpls traffic-eng affinity 0x0101 mask 0x303Related Commands
Sets the attributes for the interface.
Sets the mode of a tunnel to MPLS for traffic engineering.
tunnel mpls traffic-eng auto-bw
To configure a tunnel for automatic bandwidth adjustment and to control the manner in which the bandwidth for a tunnel is adjusted, use the tunnel mpls traffic-eng auto-bw command in interface configuration mode. To disable automatic bandwidth adjustment for a tunnel, use the no form of this command.
tunnel mpls traffic-eng auto-bw [collect-bw] [frequency seconds] [max-bw number] [min-bw number]
no tunnel mpls traffic-eng auto-bw
Syntax Description
Defaults
If the command is entered with no optional keywords or arguments, automatic bandwidth adjustment for the tunnel is enabled, with adjustments made every 24 hours and with no constraints on the bandwidth adjustments made.
If the collect-bw keyword is entered, the tunnel's bandwidth is sampled but not adjusted, and the other keywords, if any, are ignored.
If the collect-bw keyword is not entered and some, but not all of the other keywords are entered, the defaults for the options not entered are: frequency, every 24 hours; min-bw, unconstrained (0); max-bw, unconstrained.
Command Modes
Interface configuration
Command History
Usage Guidelines
To sample the bandwidth used by a tunnel without automatically adjusting it, specify the collect-bw keyword in the tunnel mpls traffic-eng auto-bw command.
If you enter the tunnel mpls traffic-eng auto-bw command without the collect-bw keyword, the tunnel's bandwidth is adjusted to the largest average output rate sampled for the tunnel since the last bandwidth adjustment for the tunnel was made.
To constrain the bandwidth adjustment that can be made to a tunnel, use the max-bw and/or min-bw keywords and specify the permitted maximum allowable bandwidth and/or minimum allowable bandwidth, respectively.
The no form of the tunnel mpls traffic-eng auto-bw command disables bandwidth adjustment for the tunnel and restores the configured bandwidth for the tunnel bandwidth where "configured bandwidth" is determined as follows:
•
If the tunnel bandwidth was explicitly configured via the tunnel mpls traffic-eng bandwidth command after the running configuration was written (if at all) to the startup configuration, the "configured bandwidth" is the bandwidth specified by that command.
•
Note
Note
Note
Examples
The following example shows how to enable automatic bandwidth adjustment for tunnel102 and specify that the adjustments are to occur every hour:
Router(config)# interface tunnel102Router(config-if)# tunnel mpls traffic-eng auto-bw frequency 3600Related Commands
Enables automatic bandwidth adjustment on a platform for tunnels configured for bandwidth adjustment.
Sets the mode of a tunnel to MPLS for traffic engineering.
tunnel mpls traffic-eng autoroute announce
To specify that the Interior Gateway Protocol (IGP) should use the tunnel (if the tunnel is up) in its enhanced shortest path first (SPF) calculation, use the tunnel mpls traffic-eng autoroute announce command in interface configuration mode. To disable this feature, use the no form of this command.
tunnel mpls traffic-eng autoroute announce
no tunnel mpls traffic-eng autoroute announce
Syntax Description
This command has no arguments or keywords.
Defaults
The IGP does not use the tunnel in its enhanced SPF calculation.
Command Modes
Interface configuration
Command History
Usage Guidelines
Currently, the only way to forward traffic onto a tunnel is by enabling this feature or by explicitly configuring forwarding (for example, with an interface static route).
Examples
The following example shows how to specify that the IGP should use the tunnel in its enhanced SPF calculation if the tunnel is up:
Router(config-if)# tunnel mpls traffic-eng autoroute announceThe following example shows how to specify that if the IGP is using this tunnel in its enhanced SPF calculation, the IGP should give it an absolute metric of 10:
Router(config-if)# tunnel mpls traffic-eng autoroute announce metric absolute 10Related Commands
ip route
Establishes static routes.
Sets the mode of a tunnel to MPLS for traffic engineering.
tunnel mpls traffic-eng autoroute metric
To specify the Multiprotocol Label Switching (MPLS) traffic engineering tunnel metric that the Interior Gateway Protocol (IGP) enhanced shortest path first (SPF) calculation uses, use the tunnel mpls traffic-eng autoroute metric command in interface configuration mode. To disable the specified MPLS traffic engineering tunnel metric, use the no form of this command.
tunnel mpls traffic-eng autoroute metric {absolute | relative} value
no tunnel mpls traffic-eng autoroute metric
Syntax Description
Defaults
The default is metric relative 0.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to specify the use of MPLS traffic engineering tunnel metric negative 1 for the IGP enhanced SPF calculation:
Router(config-if)# tunnel mpls traffic-eng autoroute metric relative -1Related Commands
Shows the tunnels announced to IGP, including interface, destination, and bandwidth.
Instructs the IGP to use the tunnel (if it is up) in its enhanced SPF calculation.
tunnel mpls traffic-eng bandwidth
To configure bandwidth required for a Multiprotocol Label Switching (MPLS) traffic engineering tunnel, use the tunnel mpls traffic-eng bandwidth command in interface configuration mode. To disable this bandwidth configuration, use the no form of this command.
tunnel mpls traffic-eng bandwidth [sub-pool | global] bandwidth
no tunnel mpls traffic-eng bandwidth [sub-pool | global] bandwidth
Syntax Description
Defaults
Default bandwidth is 0.
Default is a global pool tunnel.Command Modes
Interface configuration
Command History
12.0(5)S
This command was introduced.
12.0(11)ST
The sub-pool keyword was added.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
Usage Guidelines
Enter the bandwidth for either a global pool or subpool tunnel, not both. Only the ip rsvp bandwidth command specifies the two bandwidths within one command.
To set up only a global pool tunnel, leave out the keyword sub-pool. If you enter global as a keyword, the system will accept it, but won't write it to NVRAM. This is to avoid the problem of having your configuration not understood if you upgrade to an image that contains the DS-TE capability and then return to a non-DS-TE image.
Examples
The following example shows how to configure 100 kbps of bandwidth for the MPLS traffic engineering tunnel:
Router(config-if)# tunnel mpls traffic-eng bandwidth 100Related Commands
tunnel mpls traffic-eng load-share
To determine load-sharing among two or more Multiprotocol Label Switching (MPLS) traffic engineering (TE) tunnels that begin at the same router and go to an identical destination, use the tunnel mpls traffic-eng load-share command in interface configuration mode. To disable this feature, use the no form of this command.
tunnel mpls traffic-eng load-share value
no tunnel mpls traffic-eng load-share value
Syntax Description
value
A value from which the head-end router will calculate the proportion of traffic to be sent down each of the parallel tunnels. Range is between 1 and 1000000.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
Each parallel tunnel must be configured with this command. Specify a value to indicate the proportion of total traffic you want to be allocated into each individual tunnel. For example, if there are to be three parallel tunnels, and you want Tunnel1 to carry half of the traffic and the other two tunnels to carry one-quarter, you should enter the following values:
•
•
•
The ability to divide bandwidth in unequal amounts across traffic engineering tunnels has a finite granularity. This granularity varies by platform, with both hardware and software limits. If load-sharing is configured so that it exceeds the available granularity, the following message is displayed:
@FIB-4-UNEQUAL: Range of unequal path weightings too large for prefix x.x.x.x/y. Some available paths may not be used.To eliminate this message, it is recommended that you change the requested bandwidth or load-share.
Examples
In the following example, three tunnels are configured, with the first tunnel receiving half of the traffic and the other two tunnels receiving one-quarter:
interface Tunnel1ip unnumbered Loopback0no ip directed-broadcasttunnel destination 41.41.41.41tunnel mode mpls traffic-engtunnel mpls traffic-eng path-option 10 dynamictunnel mpls traffic-eng load-share 2interface Tunnel2ip unnumbered Loopback0no ip directed-broadcasttunnel destination 41.41.41.41tunnel mode mpls traffic-engtunnel mpls traffic-eng path-option 10 dynamictunnel mpls traffic-eng load-share 1interface Tunnel3ip unnumbered Loopback0no ip directed-broadcasttunnel destination 41.41.41.41tunnel mode mpls traffic-engtunnel mpls traffic-eng path-option 10 dynamictunnel mpls traffic-eng load-share 1Related Commands
tunnel mpls traffic-eng path-option
To configure a path option for a Multiprotocol Label Switching (MPLS) traffic engineering tunnel, use the tunnel mpls traffic-eng path-option command in interface configuration mode. To disable the specified path option, use the no form of this command.
tunnel mpls traffic-eng path-option number {dynamic | explicit {name path-name |
path-number}} [lockdown]no tunnel mpls traffic-eng path-option number {dynamic | explicit {name path-name |
path-number}} [lockdown]Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
You can configure multiple path options for a single tunnel. For example, there can be several explicit path options and a dynamic option for one tunnel. Path setup preference is for lower (not higher) numbers, so option 1 is preferred.
Examples
The following example shows how to configure the tunnel to use a named IP explicit path:
Router(config-if)# tunnel mpls traffic-eng path-option 1 explicit name testRelated Commands
tunnel mpls traffic-eng priority
To configure the setup and reservation priority for an Multiprotocol Label Switching (MPLS) traffic engineering tunnel, use the tunnel mpls traffic-eng priority command in interface configuration mode. To remove the specified setup and reservation priority, use the no form of this command.
tunnel mpls traffic-eng priority setup-priority [hold-priority]
no tunnel mpls traffic-eng priority setup-priority [hold-priority]
Syntax Description
Defaults
setup-priority: 7
hold-priority: The same value as the setup-priorityCommand Modes
Interface configuration
Command History
Usage Guidelines
When a label switched path (LSP) is being signaled and an interface does not currently have enough bandwidth available for that LSP, the call admission software preempts lower-priority LSPs so that the new LSP can be admitted. (LSPs are preempted if that allows the new LSP to be admitted.)
In the described determination, the new LSP's priority is its setup priority and the existing LSP's priority is its hold priority. The two priorities make it possible to signal an LSP with a low setup priority (so that the LSP does not preempt other LSPs on setup) but a high hold priority (so that the LSP is not preempted after it is established).
Setup priority and hold priority are typically configured to be equal, and setup priority cannot be better (numerically smaller) than the hold priority.
Examples
The following example shows how to configure a tunnel with a setup and hold priority of 1:
Router(config-if)# tunnel mpls traffic-eng priority 1Related Commands
tunnel mpls traffic-eng record-route
To include the interface address for the label switched path (LSP) in the Record Route Object (RRO) for an RESV message, use the tunnel mpls traffic-eng record-route command in interface configuration mode. To remove the interface address for the LSP in the RRO for the RESV message, use the no form of this command.
tunnel mpls traffic-eng record-route
no tunnel mpls traffic-eng record-route
Syntax Description
This command has no arguments or keywords.
Command Default
By default, this command is disabled. The interface addresses for the LSP are not included in the RRO of the RESVmessage.The record-route option is automatically enabled when the tunnel mpls traffic-eng fast-reroute command for the fast-reroute (FRR) feature is enabled at the headend.
Command Modes
Interface configuration
Command History
12.0(5)S
This command was introduced.
12.0(7)T
This command was integrated into Cisco IOS Release 12.0(7)T.
Usage Guidelines
The RRO has two functions. It records the route of the LSP that can be used in loop prevention, and it records labels that are used by FRR.
The contents of a RRO are a series of variable-length data items called subobjects.
If record route is enabled, the RRO contains details in the following order: node-ID, interface address, and label.
Examples
The following example shows how to include the interface address using the tunnel mpls traffic-eng record-route command:
interface tunnel1ip unnumbered loopback0no ip direct-broadcasttunnel destination 192.168.1.5tunnel mode mpls traffic-engtunnel mpls traffic-eng autoroute announcetunnel mpls traffic-eng bandwidth 100tunnel mpls traffic-eng priority 1 1tunnel mpls traffic-eng path-option 1 dynamictunnel mpls traffic-eng record-routeRelated Commands
,
tunnel tsp-hop
To define hops in the path for the label switching tunnel, use the tunnel tsp-hop command in interface configuration mode. To remove these hops, use the no form of this command.
tunnel tsp-hop hop-number ip-address [lasthop]
no tunnel tsp-hop hop-number ip-address [lasthop]
Syntax Description
Defaults
No hops are defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
The list of tunnel hops must specify a strict source route for the tunnel. In other words, the router at hop <n> must be directly connected to the router at hop <n>+1.
Examples
The following example shows how to configure a two-hop tunnel. The first hop router/switch is 172.16.0.2, and the second and last hop is router/switch 172.17.0.2.
Router(config)# interface tunnel 5Router(config-if)# tunnel mode mpls traffic-engRouter(config-if)# ip unnumbered e0/1Router(config-if)# tunnel tsp-hop 1 172.16.0.2Router(config-if)# tunnel tsp-hop 2 172.17.0.2 lasthopRelated Commands
vlan database
To enter virtual LAN (VLAN) configuration mode, use the vlan database command in privileged EXEC mode.
vlan database
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Once you are in VLAN configuration mode, you can access the VLAN database editing buffer manipulation commands, including:
•
•
•
•
•
•
•
•
Examples
The following example shows how to enter VLAN configuration mode:
Router# vlan databaseRouter(vlan)#The following example shows how to exit VLAN configuration mode without applying changes after you are in VLAN configuration mode:
Router(vlan)# abortAborting....Router#The following example shows how to delete a VLAN after you are in VLAN configuration mode:
Router(vlan)# no vlan 100Deleting VLAN 100...Router(vlan)#Related Commands
vlan (VLAN configuration mode)
To configure a specific virtual LAN (VLAN), use the vlan command in VLAN configuration mode. To delete a VLAN, use the no form of this command without additional options.
vlan vlan-id [are hops] [backupcrf mode] [bridge type | bridge-number] [media type] [mtu mtu-size] [name vlan-name] [parent parent-vlan-id] [ring ring-number] [said sa-id-value] [state {suspend | active}] [stp type type] [tb-vlan1 tb-vlan1-id] [tb-vlan2 tb-vlan2-id]
no vlan
Syntax Description
Defaults
The defaults are as follows:
vlan-name is VLANxxxx where xxxx represents four numeric digits (including leading zeros) equal to the VLAN ID number
media type—ethernet
state—active
said-value—100000 plus the VLAN ID number
mtu-size—dependent upon the VLAN type:•
•
•
•
•
ring-number—no ring number is specified
bridge-number—no bridge number is specified
parent-vlan-id—no parent VLAN is specified
type—no STP type is specified
tb-vlan1 and tb-vlan2—0, which means no translational bridge VLAN is specifiedCommand Modes
VLAN configuration
Command History
Usage Guidelines
VLAN 1 parameters are factory configured and cannot be changed.
When you define vlan-name, the name must be unique within the administrative domain.
The Security association ID (SAID) is documented in 802.10. When the no form is used, the VLAN's SAID is returned to the default.
When you define the said-value, the name must be unique within the administrative domain.
The bridge-number argument is used only for Token Ring-net and FDDI-net VLANs and is ignored in other types of VLANs. When the no form is used, the VLAN's source-routing bridge number returns to the default.
The parent VLAN resets to the default if the parent VLAN is deleted or the media keyword changes the VLAN type or the VLAN type of the parent VLAN.
The tb-vlan1 and tb-vlan2 keywords are used to configure translational bridge VLANs of a specified type of VLAN and are not allowed in other types of VLANs. Translational bridge VLANs must be of a differing VLAN type as the affected VLAN; if two VLANs are specified, the two must be of differing VLAN types.
A translational bridge VLAN will reset to the default if the translational bridge VLAN is deleted or the media keyword changes the VLAN type or the VLAN type of the corresponding translational bridge VLAN.
Examples
The following example shows how to add a new VLAN with all default parameters to the new VLAN database:
Router(vlan)# vlan 2
Note
The following example shows how to cause the device to add a new VLAN, specify the media type and parent VLAN ID number 3, and set all other parameters to the defaults:
Router(vlan)# vlan 2 media ethernet parent 3VLAN 2 modified:Media type ETHERNETParent VLAN 3The following example shows how to delete VLAN 2:
Router(vlan)# no vlan 2The following example shows how to return the maximum transmission unit (MTU) to the default for its type and return translational bridging VLANs to the default:
Router(vlan)# no vlan 2 mtu tb-vlan1 tb-vlan2Related Commands
show vlan
Displays VLAN information.
vlan database
Enters VLAN configuration mode.
vpn id
To set or update a Virtual Private Network (VPN) ID on a VPN routing/forwarding instance (VRF), use the vpn id command in VRF configuration mode. To remove the VPN ID from the VRF, use the no form of this command.
vpn id oui:vpn-index
no vpn id [oui:vpn-index]
Syntax Description
Defaults
The VPN ID is not set.
Command Modes
VRF configuration
Command History
Usage Guidelines
Each VRF configured in a provider edge (PE) router can have a VPN ID. Use the same VPN ID for the PE routers that belong to the same VPN. Make sure the VPN ID is unique for each VPN in the service provider network.
To change the VPN ID, issue the command again. The new ID overwrites the old one.
Examples
The following example shows how to assign the VPN ID of 0000a100003f6c to a VRF called vpn1:
Router(config)# ip vrf vpn1Router(config-vrf)# vpn id a1:3f6cRelated Commands
vtp client
To place the device in VLAN Trunking Protocol (VTP) client mode, use the vtp client command in virtual LAN (VLAN) configuration mode. To return to VTP server mode, use the no form of this command.
vtp client
no vtp client
Syntax Description
This command has no arguments or keywords.
Defaults
Server mode
Command Modes
VLAN configuration
Command History
Usage Guidelines
If the receiving switch is in client mode, the client switch changes its configuration to duplicate the configuration of the server. If you have switches in client mode, be sure to make all VTP or VLAN configuration changes on a switch in server mode.
The vtp server command is the functional equivalent of no vtp client command except that it does not return an error if the device is not in client mode.
Examples
The following example shows how to place the device in VTP client mode:
Router(vlan)# vtp clientRelated Commands
vtp domain
To configure the administrative domain name for the device, use the vtp domain command in virtual LAN (VLAN) configuration mode.
vtp domain domain-name
Syntax Description
Defaults
This command has no default setting.
Command Modes
VLAN configuration
Command History
Usage Guidelines
When you define the domain-name argument, the domain name is case sensitive.
Until a domain name is set, the device is in the no-management-domain state. In this state, the device does not transmit any VLAN Trunking Protocol (VTP) advertisements regardless of changes to local VLAN configuration. The device leaves the no-management-domain state upon receiving the first VTP summary packet on any port that is currently trunking or upon configuration of a domain name using the vtp domain command. If the device receives its domain from a summary packet, it resets its configuration revision number to zero.
Once the device leaves the no-management-domain state, it can never be configured to reenter it, except by cleaning NVRAM and reloading.
Examples
The following example shows how to set the device's administrative domain:
Router(vlan)# vtp domain DomainChandonRelated Commands
show vtp
Displays VTP statistics and domain information.
vtp (global configuration)
Modifies the name of the VTP configuration storage file.
vtp password
To create a VLAN Trunking Protocol (VTP) domain password, use the vtp password command in virtual LAN (VLAN) configuration mode. To delete the password, use the no form of this command.
vtp password password-value
no vtp password
Syntax Description
password-value
Specifies the password. The value is an ASCII string from 1 to 32 characters identifying the administrative domain for the device.
Defaults
The default is no password.
Command Modes
VLAN configuration
Command History
Usage Guidelines
The value of the password-value argument is an ASCII string from 1 to 32 characters identifying the administrative domain for the device.
Examples
The following example shows how to create a VTP domain password:
Router(vlan)# vtp password DomainChandonThe following example shows how to delete the VTP domain password:
Router(vlan)# no vtp passwordClearing device VLAN database password.Related Commands
show vtp
Displays VTP statistics and domain information.
vtp (global configuration)
Modifies the name of the VTP configuration storage file.
vtp server
To place the device in VLAN Trunking Protocol (VTP) server mode, use the vtp server command in virtual LAN (VLAN) configuration mode.
vtp server
Syntax Description
This command has no arguments or keywords.
Defaults
The default is VTP server mode.
Command Modes
VLAN configuration
Command History
Usage Guidelines
If you make a change to the VTP or VLAN configuration on a switch in server mode, that change is propagated to all the switches in the same VTP domain.
VTP can be set to either server or client mode only when dynamic VLAN creation is disabled.
If the receiving switch is in server mode, the configuration is not changed.
The vtp server command is the functional equivalent of no vtp client command except that it does not return an error if the device is not in client mode.
Examples
The following example shows how to place the device in VTP server mode:
Router(vlan)# vtp serverRelated Commands
vtp transparent
To place the device in VLAN Trunking Protocol (VTP) transparent mode, use the vtp transparent command in virtual LAN (VLAN) configuration mode. To return to VTP server mode, use the no form of this command.
vtp transparent
no vtp transparent
Syntax Description
This command has no arguments or keywords.
Defaults
The default is VTP server mode.
Command Modes
VLAN configuration
Command History
Usage Guidelines
The vtp transparent command disables VTP from the domain but does not remove the domain from the switch.
If the receiving switch is in transparent mode, the configuration is not changed. Switches in transparent mode do not participate in VTP. If you make VTP or VLAN configuration changes on a switch in transparent mode, the changes are not propagated to the other switches in the network.
The vtp server command is similar to the no vtp transparent command, except that it does not return an error if the device is not in transparent mode.
Examples
The following example shows how to place the device in VTP transparent mode:
Router(vlan)# vtp transparentThe following example shows how to return the device to VTP server mode:
Router(vlan)# no vtp transparentRelated Commands
vtp v2-mode
To enable VLAN Trunk Protocol (VTP) version 2 mode, use the vtp v2-mode command in virtual LAN (VLAN) configuration mode. To disable version 2 mode, use the no form of this command.
vtp v2-mode
no vtp v2-mode
Syntax Description
This command has no arguments or keywords.
Defaults
Version 2 mode is disabled.
Command Modes
VLAN configuration
Command History
Usage Guidelines
All switches in a VTP domain must run the same version of VTP. VTP version 1 and VTP version 2 do not operate on switches in the same VTP domain.
If all switches in a domain are VTP version 2-capable, you must enable VTP version 2 only on one switch; the version number is then propagated to the other version 2-capable switches in the VTP domain.
If you toggle the version 2 mode, parameters of certain default VLANs are modified.
Examples
The following example shows how to enable version 2 mode in the VLAN database:
Router(vlan)# vtp v2-modeThe following example shows how to disable version 2 mode in the VLAN database:
Router(vlan)# no vtp v2-modeRelated Commands
show vtp
Displays VTP statistics and domain information.
vtp (global configuration)
Modifies the name of the VTP configuration storage file.
