- trust
- udld (global configuration)
- udld (interface configuration)
- udld reset
- vlan (global configuration)
- vlan (VLAN configuration)
- vlan access-map
- vlan database
- vlan filter
- vmps reconfirm (privileged EXEC)
- vmps reconfirm (global configuration)
- vmps retry
- vmps server
- vtp (global configuration)
- vtp (VLAN configuration)
trust
Use the trust policy-map class configuration command on the switch stack or on a standalone switch to define a trust state for traffic classified through the class policy-map configuration or the class-map global configuration command. Use the no form of this command to return to the default setting.
trust [cos | dscp | ip-precedence]
no trust [cos | dscp | ip-precedence]
Syntax Description
Defaults
The action is not trusted. If no keyword is specified when the command is entered, the default is dscp.
Command Modes
Policy-map class configuration
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Use this command to distinguish the quality of service (QoS) trust behavior for certain traffic from other traffic. For example, incoming traffic with certain DSCP values can be trusted. You can configure a class map to match and trust the DSCP values in the incoming traffic.
Trust values set with this command supersede trust values set with the mls qos trust interface configuration command.
The trust command is mutually exclusive with set policy-map class configuration command within the same policy map.
If you specify trust cos, QoS uses the received or default port CoS value and the CoS-to-DSCP map to generate a DSCP value for the packet.
If you specify trust dscp, QoS uses the DSCP value from the ingress packet. For non-IP packets that are tagged, QoS uses the received CoS value; for non-IP packets that are untagged, QoS uses the default port CoS value. In either case, the DSCP value for the packet is derived from the CoS-to-DSCP map.
If you specify trust ip-precedence, QoS uses the IP precedence value from the ingress packet and the IP-precedence-to-DSCP map. For non-IP packets that are tagged, QoS uses the received CoS value; for non-IP packets that are untagged, QoS uses the default port CoS value. In either case, the DSCP for the packet is derived from the CoS-to-DSCP map.
To return to policy-map configuration mode, use the exit command. To return to privileged EXEC mode, use the end command.
Examples
This example shows how to define a port trust state to trust incoming DSCP values for traffic classified with class1:
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# trust dscp
Switch(config-pmap-c)# police 1000000 20000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
You can verify your settings by entering the show policy-map privileged EXEC command.
Related Commands
udld (global configuration)
Use the udld global configuration command on the switch stack or on a standalone switch to enable aggressive or normal mode in the UniDirectional Link Detection (UDLD) and to set the configurable message timer time. Use the no form of the command to disable aggressive or normal mode UDLD on all fiber-optic ports.
udld {aggressive | enable | message time message-timer-interval}
no udld {aggressive | enable | message}
Syntax Description
Defaults
UDLD is disabled on all interfaces.
The message timer is set at 60 seconds.
Command Modes
Global configuration
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
In normal mode, if UDLD is in the advertisement or in the detection phase and all the neighbor cache entries are aged out, UDLD restarts the link-up sequence to try to resynchronize with any potentially out-of-sync neighbors.
If you enable aggressive mode, when all the neighbors of a port have aged out either in the advertisement or in the detection phase, UDLD restarts the link-up sequence to resynchronize with any potentially out-of-sync neighbor. UDLD shuts down the port if, after the fast train of messages, the link state is still undetermined. Use aggressive mode on point-to-point links where no failure between two neighbors is allowed. In this situation, UDLD probe packets can be considered as a heart beat whose presence guarantees the health of the link. Conversely, the link must be shut down if it is not possible to re-establish a bidirectional link.
If you change the message time between probe packets, you are making a trade-off between the detection speed and the CPU load. By decreasing the time, you can make the detection-response faster but increase the load on the CPU.
This command affects fiber-optic interfaces only. Use the udld interface configuration command to enable UDLD on other interface types.
Examples
This example shows how to enable UDLD on all fiber-optic interfaces:
Switch(config)# udld enable
You can verify your setting by entering the show udld privileged EXEC command.
Related Commands
udld (interface configuration)
Use the udld interface configuration command on the switch stack or on a standalone switch to enable the UniDirectional Link Detection (UDLD) on an individual interface or prevent a fiber-optic interface from being enabled by the udld global configuration command. Use the no form of this command to return to the udld global configuration command setting or to disable UDLD if entered on a nonfiber-optic port.
udld port {aggressive | disable}
no udld port {aggressive | disable}
Syntax Description
Defaults
On fiber-optic interfaces, UDLD is not enabled, in aggressive mode, or disabled. For this reason, fiber-optic interfaces enable UDLD according to the state of the udld enable or udld aggressive global configuration command.
On nonfiber-optic interfaces, UDLD is disabled.
Command Modes
Interface configuration
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
A UDLD-capable port cannot detect a unidirectional link if it is connected to a UDLD-incapable port of another switch.
In normal mode, if UDLD is in the advertisement or in the detection phase and all the neighbor cache entries are aged out, UDLD restarts the link-up sequence to try to resynchronize with any potentially out-of-sync neighbors.
If you enable aggressive mode, after all the neighbors of a port have aged out either in the advertisement or in the detection phase, UDLD restarts the link-up sequence to resynchronize with any potentially out-of-sync neighbor. UDLD disables the port if, after the fast train of messages, the link state is still undetermined. Use aggressive mode on point-to-point links where no failure between two neighbors is allowed. In this situation, UDLD probe packets can be considered as a heart beat whose presence guarantees the health of the link. Conversely, the loss of the heart beat that the link must be shut down if it is not possible to re-establish a bidirectional link.
Use the no udld enable command on fiber-optic ports to return control of UDLD to the udld enable global configuration command or to disable UDLD on nonfiber-optic ports.
Use the udld aggressive command on fiber-optic ports to override the setting of the udld enable or udld aggressive global configuration command. Use the no form on fiber-optic ports to remove this setting and to return control of UDLD enabling to the udld global configuration command or to disable UDLD on nonfiber-optic ports.
The disable keyword is supported on fiber-optic ports only. Use the no form of this command to remove this setting and to return control of UDLD to the udld global configuration command.
If the switch software detects a GBIC module change and the port changes from fiber optic to nonfiber optic or vice versa, all configurations are maintained.
Examples
This example shows how to enable UDLD on an port 11 of stack member 6:
Switch(config)# interface gigabitethernet6/0/11
Switch(config-if)# udld enable
This example shows how to disable UDLD on a fiber-optic interface despite the setting of the udld global configuration command:
Switch(config)# interface gigabitethernet6/0/11
Switch(config-if)# udld disable
You can verify your settings by entering the show running-config or the show udld interface privileged EXEC command.
Related Commands
udld reset
Use the udld reset privileged EXEC command to reset all interfaces disabled by the UniDirectional Link Detection (UDLD) and permit traffic to begin passing through them again (though other features, such as spanning tree, Port Aggregation Protocol (PAgP), and Dynamic Trunking Protocol (DTP) still have their normal effects, if enabled).
udld reset
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
If the interface configuration is still enabled for UDLD, these ports begin to run UDLD again and are disabled for the same reason if the problem has not been corrected.
Examples
This example shows how to reset all interfaces disabled by UDLD:
Switch# udld reset
1 ports shutdown by UDLD were reset.
You can verify your setting by entering the show udld privileged EXEC command.
Related Commands
vlan (global configuration)
Use the vlan global configuration command on the switch stack or on a standalone switch to add a VLAN and to enter the config-vlan mode. Use the no form of this command to delete the VLAN. Configuration information for normal-range VLANs (VLAN IDs 1 to 1005) is always saved in the VLAN database. When VLAN Trunking Protocol (VTP) mode is transparent, you can create extended-range VLANs (VLAN IDs greater than 1005), and the VTP mode, domain name, and the VLAN configuration are saved in the switch running configuration file. You can save configurations in the switch startup configuration file by entering the copy running-config startup-config privileged EXEC command.
vlan vlan-id
no vlan vlan-id
Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You must use the vlan vlan-id global configuration command to add extended-range VLANs (VLAN IDs 1006 to 4094). Before configuring VLANs in the extended range, you must use the vtp transparent global configuration or VLAN configuration command to put the switch in VTP transparent mode. Extended-range VLANs are not learned by VTP and are not added to the VLAN database, but when VTP mode is transparent, VTP mode and domain name and all VLAN configurations are saved in the running configuration, and you can save them in the switch startup configuration file.
When you save the VLAN and VTP configurations in the startup configuration file and reboot the switch, the configuration is determined in these ways:
•
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 VTP mode is server, or if the startup VTP mode or domain names do not match the VLAN database, the VTP mode and the VLAN configuration for the first 1005 VLANs use the VLAN database information.
If you try to create an extended-range VLAN when the switch is not in VTP transparent mode, the VLAN is rejected, and you receive an error message.
If you enter an invalid VLAN ID, you receive an error message and do not enter config-vlan mode.
Entering the vlan command with a VLAN ID enables config-vlan mode. When you enter the VLAN ID of an existing VLAN, you do not create a new VLAN, but you can modify VLAN parameters for that VLAN. The specified VLANs are added or modified when you exit the config-vlan mode. Only the shutdown command (for VLANs 1 to 1005) takes effect immediately.
These configuration commands are available in config-vlan mode. The no form of each command returns the characteristic to its default state.
Note Although all commands are visible, the only config-vlan command supported on extended-range VLANs is mtu mtu-size. For extended-range VLANs, all other characteristics must remain at the default state.
•are are-number: defines the maximum number of all-routes explorer (ARE) hops for this VLAN. This keyword applies only to TrCRF VLANs.The range is 0 to 13. The default is 7. If no value is entered, 0 is assumed to be the maximum.
•backupcrf: specifies the backup CRF mode. This keyword applies only to TrCRF VLANs.
–enable backup CRF mode for this VLAN.
–disable backup CRF mode for this VLAN (the default).
•bridge {bridge-number| type}: specifies the logical distributed source-routing bridge, the bridge that interconnects all logical rings having this VLAN as a parent VLAN in FDDI-NET, Token Ring-NET, and TrBRF VLANs. The range is 0 to 15. The default bridge number is 0 (no source-routing bridge) for FDDI-NET, TrBRF, and Token Ring-NET VLANs. The type keyword applies only to TrCRF VLANs and is one of these:
–srb (source-route bridging)
–srt (source-route transparent) bridging VLAN
•exit: applies changes, increments the VLAN database revision number (VLANs 1 to 1005 only), and exits config-vlan mode.
•media: defines the VLAN media type. See Table 2-24 for valid commands and syntax for different media types.
Note The switch supports only Ethernet ports. You configure only FDDI and Token Ring media-specific characteristics for VLAN Trunking Protocol (VTP) global advertisements to other switches. These VLANs are locally suspended.
–ethernet is Ethernet media type (the default).
–fddi is FDDI media type.
–fd-net is FDDI network entity title (NET) media type.
–tokenring is Token Ring media type if the VTP v2 mode is disabled, or TrCRF if the VTP version 2 (v) mode is enabled.
–tr-net is Token Ring network entity title (NET) media type if the VTP v2 mode is disabled or TrBRF media type if the VTP v2 mode is enabled.
•mtu mtu-size: specifies the maximum transmission unit (MTU) (packet size in bytes). The range is 1500 to 18190. The default is 1500 bytes.
•name vlan-name: names the VLAN with an ASCII string from 1 to 32 characters that must be unique within the administrative domain. The default is VLANxxxx where xxxx represents four numeric digits (including leading zeros) equal to the VLAN ID number.
•no: negates a command or returns it to the default setting.
•parent parent-vlan-id: specifies the parent VLAN of an existing FDDI, Token Ring, or TrCRF VLAN. This parameter identifies the TrBRF to which a TrCRF belongs and is required when defining a TrCRF. The range is 0 to 1005. The default parent VLAN ID is 0 (no parent VLAN) for FDDI and Token Ring VLANs. For both Token Ring and TrCRF VLANs, the parent VLAN ID must already exist in the database and be associated with a Token Ring-NET or TrBRF VLAN.
Note Though visible in the command-line interface, the private-vlan command is not supported.
•remote-span: configure the VLAN as a Remote SPAN (RSPAN) VLAN. When the RSPAN feature is added to an existing VLAN, the VLAN is first deleted and is then recreated with the RSPAN feature. Any access ports are deactivated until the RSPAN feature is removed. If VTP is enabled, the new RSPAN VLAN is propagated by VTP for VLAN-IDs that are lower than 1024. Learning is disabled on the VLAN. See the remote-span command for more information.
•ring ring-number: defines the logical ring for an FDDI, Token Ring, or TrCRF VLAN. The range is 1 to 4095. The default for Token Ring VLANs is 0. For FDDI VLANs, there is no default.
•said said-value: specifies the security association identifier (SAID) as documented in IEEE 802.10. The range is 1 to 4294967294, and the number must be unique within the administrative domain. The default value is 100000 plus the VLAN ID number.
•shutdown: shuts down VLAN switching on the VLAN. This command takes effect immediately. Other commands take effect when you exit config-vlan mode.
•state: specifies the VLAN state:
–active means the VLAN is operational (the default).
–suspend means the VLAN is suspended. Suspended VLANs do not pass packets.
•ste ste-number: defines the maximum number of spanning-tree explorer (STE) hops. This keyword applies only to TrCRF VLANs. The range is 0 to 13. The default is 7.
•stp type: defines the spanning-tree type for FDDI-NET, Token Ring-NET, or TrBRF VLANs. For FDDI-NET VLANs, the default STP type is ieee. For Token Ring-NET VLANs, the default STP type is ibm. For FDDI and Token Ring VLANs, the default is no type specified.
–ieee for IEEE Ethernet STP running source-route transparent (SRT) bridging.
–ibm for IBM STP running source-route bridging (SRB).
–auto for STP running a combination of source-route transparent bridging (IEEE) and source-route bridging (IBM).
•tb-vlan1 tb-vlan1-id and tb-vlan2 tb-vlan2-id: specifies the first and second VLAN to which this VLAN is translationally bridged. Translational VLANs translate FDDI or Token Ring to Ethernet, for example. The range is 0 to 1005. If no value is specified, 0 (no transitional bridging) is assumed.
Table 2-25 describes the rules for configuring VLANs.
Examples
This example shows how to add an Ethernet VLAN with default media characteristics. The default includes a vlan-name of VLANxxx, where xxxx represents four numeric digits (including leading zeros) equal to the VLAN ID number. The default media option is ethernet; the state option is active. The default said-value variable is 100000 plus the VLAN ID; the mtu-size variable is 1500; the stp-type option is ieee. When you enter the exit config-vlan configuration command, the VLAN is added if it did not already exist; otherwise, this command does nothing.
This example shows how to create a new VLAN with all default characteristics and enter config-vlan mode:
Switch(config)# vlan 200
Switch(config-vlan)# exit
Switch(config)#
This example shows how to create a new extended-range VLAN with all the default characteristics, to enter config-vlan mode, and to save the new VLAN in the switch startup configuration file:
Switch(config)# vtp mode transparent
Switch(config)# vlan 2000
Switch(config-vlan)# end
Switch# copy running-config startup config
You can verify your setting by entering the show vlan privileged EXEC command.
Related Commands
vlan (VLAN configuration)
Use the vlan VLAN configuration command on the switch stack or on a standalone switch to configure VLAN characteristics for a normal-range VLAN (VLAN IDs 1 to 1005) in the VLAN database. You access VLAN configuration mode by entering the vlan database privileged EXEC command. Use the no form of this command without additional parameters to delete a VLAN. Use the no form with parameters to change its configured characteristics.
vlan vlan-id [are are-number] [backupcrf {enable | disable}] [bridge bridge-number |
type {srb | srt}] [media {ethernet | fddi | fdi-net | tokenring | tr-net}] [mtu mtu-size]
[name vlan-name] [parent parent-vlan-id] [ring ring-number] [said said-value]
[state {suspend | active}] [ste ste-number] [stp type {ieee | ibm | auto}]
[tb-vlan1 tb-vlan1-id] [tb-vlan2 tb-vlan2-id]
no vlan vlan-id [are are-number] [backupcrf {enable | disable}] [bridge bridge-number |
type {srb | srt}] [media {ethernet | fddi | fdi-net | tokenring | tr-net}] [mtu mtu-size]
[name vlan-name] [parent parent-vlan-id] [ring ring-number] [said said-value]
[state {suspend | active}] [ste ste-number] [stp type {ieee | ibm | auto}]
[tb-vlan1 tb-vlan1-id] [tb-vlan2 tb-vlan2-id]
Extended-range VLANs (with VLAN IDs from 1006 to 4094) cannot be added or modified by using these commands. To add extended-range VLANs, use the vlan (global configuration) command to enter config-vlan mode.
Note The switch supports only Ethernet ports. You configure only FDDI and Token Ring media-specific characteristics for VLAN Trunking Protocol (VTP) global advertisements to other switches. These VLANs are locally suspended.
Syntax Description
vlan-id |
ID of the configured VLAN. The range is 1 to 1005 and must be unique within the administrative domain. Do not enter leading zeros. |
are are-number |
(Optional) Specify the maximum number of all-routes explorer (ARE) hops for this VLAN. This keyword applies only to TrCRF VLANs. The range is 0 to 13. If no value is entered, 0 is assumed to be the maximum. |
backupcrf {enable | disable} |
(Optional) Specify the backup CRF mode. This keyword applies only to TrCRF VLANs. • • |
bridge bridge-number| |
(Optional) Specify the logical distributed source-routing bridge, the bridge that interconnects all logical rings having this VLAN as a parent VLAN in FDDI-NET, Token Ring-NET, and TrBRF VLANs. The range is 0 to 15. The type keyword applies only to TrCRF VLANs and is one of these: • • |
media {ethernet | fddi | fd-net | tokenring | tr-net} |
(Optional) Specify the VLAN media type. Table 2-26 lists the valid syntax for each media type. • • • • • |
mtu mtu-size |
(Optional) Specify the maximum transmission unit (MTU) (packet size in bytes). The range is 1500 to 18190. |
name vlan-name |
(Optional) Specify the VLAN name, an ASCII string from 1 to 32 characters that must be unique within the administrative domain. |
parent parent-vlan-id |
(Optional) Specify the parent VLAN of an existing FDDI, Token Ring, or TrCRF VLAN. This parameter identifies the TrBRF to which a TrCRF belongs and is required when defining a TrCRF. The range is 0 to 1005. |
ring ring-number |
(Optional) Specify the logical ring for an FDDI, Token Ring, or TrCRF VLAN. The range is 1 to 4095. |
said said-value |
(Optional) Enter the security association identifier (SAID) as documented in IEEE 802.10. TThe range is 1 to 4294967294, and the number must be unique within the administrative domain. |
state {suspend | active} |
(Optional) Specify the VLAN state: • • |
ste ste-number |
(Optional) Specify the maximum number of spanning-tree explorer (STE) hops. This keyword applies only to TrCRF VLANs. The range is 0 to 13. |
stp type {ieee | ibm | auto} |
(Optional) Specify the spanning-tree type for FDDI-NET, Token Ring-NET, or TrBRF VLAN. • • • |
tb-vlan1 tb-vlan1-id and tb-vlan2 tb-vlan2-id |
(Optional) Specify the first and second VLAN to which this VLAN is translationally bridged. Translational VLANs translate FDDI or Token Ring to Ethernet, for example. The range is 0 to 1005. Zero is assumed if no value is specified. |
Table 2-26 shows the valid syntax options for different media types.
Table 2-27 describes the rules for configuring VLANs.
Defaults
The ARE value is 7.
Backup CRF is disabled.
The bridge number is 0 (no source-routing bridge) for FDDI-NET, TrBRF, and Token Ring-NET VLANs.
The media type is ethernet.
The default mtu size is 1500 bytes.
The vlan-name variable is VLANxxxx, where xxxx represents four numeric digits (including leading zeros) equal to the VLAN ID number.
The parent VLAN ID is 0 (no parent VLAN) for FDDI and Token Ring VLANs. For TrCRF VLANs, you must specify a parent VLAN ID. For both Token Ring and TrCRF VLANs, the parent VLAN ID must already exist in the database and be associated with a Token Ring-NET or TrBRF VLAN.
The ring number for Token Ring VLANs is 0. For FDDI VLANs, there is no default.
The said value is 100000 plus the VLAN ID.
The state is active.
The STE value is 7.
The STP type is ieee for FDDI-NET and ibm for Token Ring-NET VLANs. For FDDI and Token Ring VLANs, the default is no type specified.
The tb-vlan1-id and tb-vlan2-id variables are zero (no translational bridging).
Command Modes
VLAN configuration
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You can only use this command mode for configuring normal-range VLANs, that is, VLAN IDs 1 to 1005.
Note To configure extended-range VLANs (VLAN IDs 1006 to 4094), use the vlan global configuration command.
VLAN configuration is always saved in the VLAN database. If VTP mode is transparent, it is also saved in the switch running configuration file, along with the VTP mode and domain name. You can then save it in the switch startup configuration file by using the copy running-config startup-config privileged EXEC command.
When you save VLAN and VTP configuration in the startup configuration file and reboot the switch, the configuration is determined in these ways:
•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 VTP mode is server, or if the startup VTP mode or domain names do not match the VLAN database, the VTP mode and the VLAN configuration for the first 1005 VLANs use VLAN database information.
The following are the results of using the no vlan commands:
•When the no vlan vlan-id form is used, the VLAN is deleted. Deleting VLANs automatically resets to zero any other parent VLANs and translational bridging parameters that refer to the deleted VLAN.
•When the no vlan vlan-id bridge form is used, the VLAN source-routing bridge number returns to the default (0). The vlan vlan-id bridge command is used only for FDDI-NET and Token Ring-NET VLANs and is ignored in other VLAN types.
•When the no vlan vlan-id media form is used, the media type returns to the default (ethernet). Changing the VLAN media type (including the no form) resets the VLAN MTU to the default MTU for the type (unless the mtu keyword is also present in the command). It also resets the VLAN parent and translational bridging VLAN to the default (unless the parent, tb-vlan1, or tb-vlan2 are also present in the command).
•When the no vlan vlan-id mtu form is used, the VLAN MTU returns to the default for the applicable VLAN media type. You can also modify the MTU by using the media keyword.
•When the no vlan vlan-id name vlan-name form is used, the VLAN name returns to the default name (VLANxxxx, where xxxx represent four numeric digits [including leading zeros] equal to the VLAN ID number).
•When the no vlan vlan-id parent form is used, the parent VLAN returns to the default (0). The parent VLAN resets to the default if the parent VLAN is deleted or if the media keyword changes the VLAN type or the VLAN type of the parent VLAN.
•When the no vlan vlan-id ring form is used, the VLAN logical ring number returns to the default (0).
•When the no vlan vlan-id said form is used, the VLAN SAID returns to the default (100,000 plus the VLAN ID).
•When the no vlan vlan-id state form is used, the VLAN state returns to the default (active).
•When the no vlan vlan-id stp type form is used, the VLAN spanning-tree type returns to the default (ieee).
•When the no vlan vlan-id tb-vlan1 or no vlan vlan-id tb-vlan2 form is used, the VLAN translational bridge VLAN (or VLANs, if applicable) returns to the default (0). Translational bridge VLANs must be a different VLAN type than the affected VLAN, and if two are specified, the two must be different VLAN types from each other. A translational bridge VLAN resets to the default if the translational bridge VLAN is deleted, if the media keyword changes the VLAN type, or if the media keyword changes the VLAN type of the corresponding translation bridge VLAN.
Examples
This example shows how to add an Ethernet VLAN with default media characteristics. The default includes a vlan-name of VLANxxx, where xxxx represents four numeric digits (including leading zeros) equal to the VLAN ID number. The default media option is ethernet; the state option is active. The default said-value variable is 100000 plus the VLAN ID; the mtu-size variable is 1500; the stp-type option is ieee. When you enter the exit or apply vlan configuration command, the VLAN is added if it did not already exist; otherwise, this command does nothing.
Switch(vlan)# vlan 2
VLAN 2 added:
Name: VLAN0002
Switch(vlan)# exit
APPLY completed.
Exiting....
This example shows how to modify an existing VLAN by changing its name and MTU size:
Switch(vlan)# no vlan name engineering mtu 1200
You can verify your settings by entering the show vlan privileged EXEC command.
Related Commands
vlan access-map
Use the vlan access-map global configuration command on the switch stack or on a standalone switch to create or modify a VLAN map entry for VLAN packet filtering. This entry changes the mode to the VLAN access map configuration. Use the no form of this command to delete a VLAN map entry. Use the vlan filter interface configuration command to apply a VLAN map to one or more VLANs.
vlan access-map name [number]
no vlan access-map name [number]
Syntax Description
Defaults
There are no VLAN map entries and no VLAN maps applied to a VLAN.
Command Modes
Global configuration
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
In global configuration mode, use this command to create or modify a VLAN map. This entry changes the mode to VLAN access-map configuration, where you can use the match access-map configuration command to specify the access lists for IP or non-IP traffic to match and use the action command to set whether a match causes the packet to be forwarded or dropped.
In VLAN access map configuration mode, these commands are available:
•action: sets the action to be taken (forward or drop).
• default: sets a command to its defaults
• exit: exits from VLAN access-map configuration mode
• match: sets the values to match (IP address or MAC address).
• no: negates a command or set its defaults
When you do not specify an entry number (sequence number), it is added to the end of the map.
There can be only one VLAN map per VLAN and it is applied as packets are received by a VLAN.
You can use the no vlan access-map name [number] command with a sequence number to delete a single entry.
In global configuration mode, use the vlan filter interface configuration command to apply the map to one or more VLANs.
Note For more information about VLAN map entries, refer to the software configuration guide for this release.
Examples
This example shows how to create a VLAN map named vac1 and apply matching conditions and actions to it. If no other entries already exist in the map, this will be entry 10.
Switch(config)# vlan access-map vac1
Switch(config-access-map)# match ip address acl1
Switch(config-access-map)# action forward
This example shows how to delete VLAN map vac1:
Switch(config)# no vlan access-map vac1
Related Commands
vlan database
Use the vlan database privileged EXEC command on the switch stack or on a standalone switch to enter VLAN configuration mode. From this mode, you can add, delete, and modify VLAN configurations for normal-range VLANs and globally propagate these changes by using the VLAN Trunking Protocol (VTP). Configuration information is saved in the VLAN database.
vlan database
Note VLAN configuration mode is only valid for VLAN IDs 1 to 1005.
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You can use the VLAN database configuration commands to configure VLANs 1 to 1005. To configure extended-range VLANs (VLAN IDs 1006 to 4094), use the vlan (global configuration) command to enter config-vlan mode. You can also configure VLAN IDs 1 to 1005 by using the vlan global configuration command.
To return to the privileged EXEC mode from the VLAN configuration mode, enter the exit command.
Note This command mode is different from other modes because it is session-oriented. When you add, delete, or modify VLAN parameters, the changes are not applied until you exit the session by entering the apply or exit command. When the changes are applied, the VTP configuration version is incremented. You can also not apply the changes to the VTP database by entering abort.
When you are in VLAN configuration mode, you can access the VLAN database and make changes by using these commands:
•vlan: accesses subcommands to add, delete, or modify values associated with a single VLAN. For more information, see the vlan (VLAN configuration) command.
•vtp: accesses subcommands to perform VTP administrative functions. For more information, see the vtp (VLAN configuration) command.
When you have modified VLAN or VTP parameters, you can use these editing buffer manipulation commands:
•abort: exits the mode without applying the changes. The VLAN configuration that was running before you entered VLAN configuration mode continues to be used.
•apply: applies current changes to the VLAN database, increments the database configuration revision number, propagates it throughout the administrative domain, and remains in VLAN configuration mode.
Note You cannot use this command when the switch is in VTP client mode.
•exit: applies all configuration changes to the VLAN database, increments the database configuration number, propagates it throughout the administrative domain, and returns to privileged EXEC mode.
•no: negates a command or set its defaults; valid values are vlan and vtp.
•reset: abandons proposed changes to the VLAN database, resets the proposed database to the implemented VLAN database on the switch, and remains in VLAN configuration mode.
•show: displays VLAN database information.
•show changes [vlan-id]: displays the differences between the VLAN database on the switch and the proposed VLAN database for all normal-range VLAN IDs (1 to 1005) or the specified VLAN ID (1 to 1005).
•show current [vlan-id]: displays the VLAN database on the switch or on a selected VLAN (1 to 1005).
•show proposed [vlan-id]: displays the proposed VLAN database or a selected VLAN (1 to 1005) from the proposed database. The proposed VLAN database is not the running configuration until you use the exit or apply VLAN configuration command.
You can verify that VLAN database changes have been made or aborted by using the show vlan privileged EXEC command. This output is different from the show VLAN database configuration command output.
Examples
This example shows how to enter the VLAN configuration mode from the privileged EXEC mode and to display VLAN database information:
Switch# vlan database
Switch(vlan)# show
VLAN ISL Id: 1
Name: default
Media Type: Ethernet
VLAN 802.10 Id: 100001
State: Operational
MTU: 1500
Translational Bridged VLAN: 1002
Translational Bridged VLAN: 1003
VLAN ISL Id: 2
Name: VLAN0002
Media Type: Ethernet
VLAN 802.10 Id: 100002
State: Operational
MTU: 1500
VLAN ISL Id: 1002
Name: fddi-default
Media Type: FDDI
VLAN 802.10 Id: 101002
State: Operational
MTU: 1500
Bridge Type: SRB
Ring Number: 0
Translational Bridged VLAN: 1
Translational Bridged VLAN: 1003
<output truncated>
This is an example of output from the show changes command:
Switch(vlan)# show changes
DELETED:
VLAN ISL Id: 4
Name: VLAN0004
Media Type: Ethernet
VLAN 802.10 Id: 100004
State: Operational
MTU: 1500
MODIFIED:
VLAN ISL Id: 7
Current State: Operational
Modified State: Suspended
This example shows how to display the differences between VLAN 7 in the current database and the proposed database.
Switch(vlan)# show changes 7
MODIFIED:
VLAN ISL Id: 7
Current State: Operational
Modified State: Suspended
This is an example of output from the show current 20 command. It displays only VLAN 20 of the current database.
Switch(vlan)# show current 20
VLAN ISL Id: 20
Name: VLAN0020
Media Type: Ethernet
VLAN 802.10 Id: 100020
State: Operational
MTU: 1500
Related Commands
vlan filter
Use the vlan filter global configuration command on the switch stack or on a standalone switch to apply a VLAN map to one or more VLANs. Use the no form of this command to remove the map.
vlan filter mapname vlan-list list
no vlan filter mapname vlan-list list
Syntax Description
mapname |
Name of the VLAN map entry. |
list |
The list of one or more VLANs in the form tt, uu-vv, xx, yy-zz, where spaces around commas and dashes are optional. The range is 1 to 4094. |
Defaults
There are no VLAN filters.
Command Modes
Global configuration
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
To avoid accidentally dropping too many packets and disabling connectivity in the middle of the configuration process, we recommend that you completely define the VLAN access map before applying it to a VLAN.
Note For more information about VLAN map entries, refer to the software configuration guide for this release.
Examples
This example applies VLAN map entry map1 to VLANs 20 and 30:
Switch(config)# vlan filter map1 vlan-list 20, 30
This example shows how to delete VLAN map entry mac1 from VLAN 20:
Switch(config)# no vlan filter map1 vlan-list 20
You can verify your settings by entering the show vlan filter privileged EXEC command.
Related Commands
vmps reconfirm (privileged EXEC)
Use the vmps reconfirm privileged EXEC command on the switch stack or on a standalone switch to immediately send VLAN Query Protocol (VQP) queries to reconfirm all dynamic VLAN assignments with the VLAN Membership Policy Server (VMPS).
vmps reconfirm
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Examples
This example shows how to immediately send VQP queries to the VMPS:
Switch# vmps reconfirm
You can verify your setting by entering the show vmps privileged EXEC command and examining the VMPS Action row of the Reconfirmation Status section. The show vmps command shows the result of the last time the assignments were reconfirmed either because the reconfirmation timer expired or because the vmps reconfirm command was entered.
Related Commands
|
|
|
|---|---|
Displays VQP and VMPS information. |
|
Changes the reconfirmation interval for the VLAN Query Protocol (VQP) client. |
vmps reconfirm (global configuration)
Use the vmps reconfirm global configuration command on the switch stack or on a standalone switch to change the reconfirmation interval for the VLAN Query Protocol (VQP) client. Use the no form of this command to return to the default setting.
vmps reconfirm interval
no vmps reconfirm
Syntax Description
interval |
Reconfirmation interval for VQP client queries to the VLAN Membership Policy Server (VMPS) to reconfirm dynamic VLAN assignments. The range is 1 to 120 minutes. |
Defaults
The default reconfirmation interval is 60 minutes.
Command Modes
Global configuration
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Examples
This example shows how to set the VQP client to reconfirm dynamic VLAN entries every 20 minutes:
Switch(config)# vmps reconfirm 20
You can verify your setting by entering the show vmps privileged EXEC command and examining information in the Reconfirm Interval row.
Related Commands
|
|
|
|---|---|
Displays VQP and VMPS information. |
|
Sends VQP queries to reconfirm all dynamic VLAN assignments with the VMPS. |
vmps retry
Use the vmps retry global configuration command on the switch stack or on a standalone switch to configure the per-server retry count for the VLAN Query Protocol (VQP) client. Use the no form of this command to return to the default setting.
vmps retry count
no vmps retry
Syntax Description
count |
Number of attempts to contact the VLAN Membership Policy Server (VMPS) by the client before querying the next server in the list. The range is 1 to 10. |
Defaults
The default retry count is 3.
Command Modes
Global configuration
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Examples
This example shows how to set the retry count to 7:
Switch(config)# vmps retry 7
You can verify your setting by entering the show vmps privileged EXEC command and examining information in the Server Retry Count row.
Related Commands
|
|
|
|---|---|
Displays VQP and VMPS information. |
vmps server
Use the vmps server global configuration command on the switch stack or on a standalone switch to configure the primary VLAN Membership Policy Server (VMPS) and up to three secondary servers. Use the no form of this command to remove a VMPS server.
vmps server ipaddress [primary]
no vmps server [ipaddress]
Syntax Description
Defaults
No primary or secondary VMPS servers are defined.
Command Modes
Global configuration
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The first server entered is automatically selected as the primary server whether or not primary is entered. The first server address can be overridden by using primary in a subsequent command.
If a member switch in a cluster configuration does not have an IP address, the cluster does not use the VMPS server configured for that member switch. Instead, the cluster uses the VMPS server on the command switch, and the command switch proxies the VMPS requests. The VMPS server treats the cluster as a single switch and uses the IP address of the command switch to respond to requests.
When using the no form without specifying the ipaddress, all configured servers are deleted. If you delete all servers when dynamic-access ports are present, the switch cannot forward packets from new sources on these ports because it cannot query the VMPS.
Examples
This example shows how to configure the server with IP address 191.10.49.20 as the primary VMPS server. The servers with IP addresses 191.10.49.21 and 191.10.49.22 are configured as secondary servers:
Switch(config)# vmps server 191.10.49.20 primary
Switch(config)# vmps server 191.10.49.21
Switch(config)# vmps server 191.10.49.22
This example shows how to delete the server with IP address 191.10.49.21:
Switch(config)# no vmps server 191.10.49.21
You can verify your setting by entering the show vmps privileged EXEC command and examining information in the VMPS Domain Server row.
Related Commands
|
|
|
|---|---|
Displays VQP and VMPS information. |
vtp (global configuration)
Use the vtp global configuration command on the switch stack or on a standalone switch to set or modify the VLAN Trunking Protocol (VTP) configuration characteristics. Use the no form of this command to remove the settings or to return to the default settings.
vtp {domain domain-name | file filename | interface name | mode {client | server | transparent} | password password | pruning | version number}
no vtp {file | interface | mode | password | pruning | version}
Syntax Description
Defaults
The default filename is flash:vlan.dat.
The default mode is server mode.
No domain name or password is defined.
No password is configured.
Pruning is disabled.
The default version is version 1.
Command Modes
Global configuration
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
When you save VTP mode, domain name, and VLAN configurations in the switch startup configuration file and reboot the switch, the VTP and VLAN configurations are determined by these conditions:
•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 determined by VLAN database information, and VLANs greater than 1005 are configured from the switch configuration file.
The vtp file filename cannot be used to load a new database; it renames only the file in which the existing database is stored.
Follow these guidelines when configuring a VTP domain name:
•The switch is in the no-management-domain state until you configure a domain name. While in the no-management-domain state, the switch does not send any VTP advertisements even if changes occur to the local VLAN configuration. The switch leaves the no-management-domain state after it receives the first VTP summary packet on any port that is trunking or after you configure a domain name by using the vtp domain command. If the switch receives its domain from a summary packet, it resets its configuration revision number to 0. After the switch leaves the no-management-domain state, it can no be configured to re-enter it until you clear the nonvolatile RAM (NVRAM) and reload the software.
•Domain names are case-sensitive.
•After you configure a domain name, it cannot be removed. You can only reassign it to a different domain.
Follow these guidelines when setting VTP mode:
•The no vtp mode command returns the switch to VTP server mode.
•The vtp mode server command is the same as no vtp mode except that it does not return an error if the switch is not in client or transparent mode.
•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. If the receiving switch is in server mode or transparent mode, the switch 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 other switches in the network.
•If you change the VTP or VLAN configuration on a switch that is in server mode, that change is propagated to all the switches in the same VTP domain.
•The vtp mode transparent command disables VTP from the domain but does not remove the domain from the switch.
•The VTP mode must be transparent for you to add extended-range VLANs or for VTP and VLAN information to be saved in the running configuration file.
•If extended-range VLANs are configured on the switch and you attempt to set the VTP mode to server or client, you receive an error message, and the configuration is not allowed.
•VTP can be set to either server or client mode only when dynamic VLAN creation is disabled.
Follow these guidelines when setting a VTP password:
•Passwords are case sensitive. Passwords should match on all switches in the same domain.
•When you use the no vtp password form of the command, the switch returns to the no-password state.
Follow these guidelines when setting VTP pruning:
•VTP pruning removes information about each pruning-eligible VLAN from VTP updates if there are no stations belonging to that VLAN.
•If you enable pruning on the VTP server, it is enabled for the entire management domain for VLAN IDs 1 to 1005.
•Only VLANs in the pruning-eligible list can be pruned.
•Pruning is supported with VTP version 1 and version 2.
Follow these guidelines when setting the VTP version:
•Toggling the version 2 (v2) mode state modifies parameters of certain default VLANs.
•Each VTP switch automatically detects the capabilities of all the other VTP devices. To use version 2, all VTP switches in the network must support version 2; otherwise, you must configure them to operate in VTP version 1 mode.
•If all switches in a domain are VTP version 2-capable, you need only to configure version 2 on one switch; the version number is then propagated to the other version-2 capable switches in the VTP domain.
•If you are using VTP in a Token Ring environment, VTP version 2 must be enabled.
•If you are configuring a Token Ring bridge relay function (TrBRF) or Token Ring concentrator relay function (TrCRF) VLAN media type, you must use version 2.
•If you are configuring a Token Ring or Token Ring-NET VLAN media type, you must use version 1.
You cannot save password, pruning, and version configurations in the switch configuration file.
Examples
This example shows how to rename the filename for VTP configuration storage to vtpfilename:
Switch(config)# vtp file vtpfilename
This example shows how to clear the device storage filename:
Switch(config)# no vtp file vtpconfig
Clearing device storage filename.
This example shows how to specify the name of the interface providing the VTP updater ID for this device:
Switch(config)# vtp interface gigabitethernet
This example shows how to set the administrative domain for the switch:
Switch(config)# vtp domain OurDomainName
This example shows how to place the switch in VTP transparent mode:
Switch(config)# vtp mode transparent
This example shows how to configure the VTP domain password:
Switch(config)# vtp password ThisIsOurDomain'sPassword
This example shows how to enable pruning in the VLAN database:
Switch(config)# vtp pruning
Pruning switched ON
This example shows how to enable version 2 mode in the VLAN database:
Switch(config)# vtp version 2
You can verify your settings by entering the show vtp status privileged EXEC command.
Related Commands
|
|
|
|---|---|
show vtp status |
Displays the VTP statistics for the switch and general information about the VTP management domain status. |
Configures VTP domain-name, password, pruning, version, and mode. |
vtp (VLAN configuration)
Use the vtp VLAN configuration command on the switch stack or on a standalone switch to configure VLAN Trunking Protocol (VTP) characteristics. You access VLAN configuration mode by entering the vlan database privileged EXEC command. Use the no form of this command to return to the default settings, disable the characteristic, or remove the password.
vtp {domain domain-name | password password | pruning | v2-mode | {server | client | transparent}}
no vtp {client | password | pruning | transparent | v2-mode}
Note VTP configuration in VLAN configuration mode is saved in the VLAN database when applied.
Syntax Description
Defaults
The default mode is server mode.
No domain name is defined.
No password is configured.
Pruning is disabled.
VTP version 2 (v2 mode) is disabled.
Command Modes
VLAN configuration
Command History
|
|
|
|---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
If the VTP mode is transparent, the mode and domain name are saved in the switch running configuration file, and you can save the configuration in the switch startup configuration file by using the copy running-config startup-config privileged EXEC command.
Follow these guidelines when setting the VTP mode:
•The no vtp client and no vtp transparent forms of the command return the switch to VTP server mode.
•The vtp server command is the same as no vtp client or no vtp transparent except that it does not return an error if the switch is not in client or transparent mode.
•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, make sure to make all VTP or VLAN configuration changes on a switch in server mode. If the receiving switch is in server mode or transparent mode, the switch 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 other switches in the network.
•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.
•The vtp transparent command disables VTP from the domain but does not remove the domain from the switch.
•The VTP mode must be transparent for you to add extended-range VLANs or for the VTP and the VLAN configurations to be saved in the running configuration file.
•If extended-range VLANs are configured on the switch and you attempt to set the VTP mode to server or client, you receive an error message and the configuration is not allowed.
•VTP can be set to either server or client mode only when dynamic VLAN creation is disabled.
Follow these guidelines when configuring a VTP domain name:
•The switch is in the no-management-domain state until you configure a domain name. While in the no-management-domain state, the switch does not send any VTP advertisements even if changes occur to the local VLAN configuration. The switch leaves the no-management-domain state after receiving the first VTP summary packet on any port that is currently trunking or after configuring a domain name with the vtp domain command. If the switch receives its domain from a summary packet, it resets its configuration revision number to zero. After the switch leaves the no-management-domain state, it can never be configured to reenter it until you clear the nonvolatile RAM (NVRAM) and reload the software.
•Domain names are case sensitive.
•After you configure a domain name, it cannot be removed. You can reassign it only to a different domain.
Follow these guidelines when configuring a VTP password:
•Passwords are case sensitive. Passwords should match on all switches in the same domain.
•When the no vtp password form of the command is used, the switch returns to the no-password state.
Follow these guidelines when enabling VTP pruning:
•If you enable pruning on the VTP server, it is enabled for the entire management domain.
•Only VLANs included in the pruning-eligible list can be pruned.
•Pruning is supported with VTP version 1 and version 2.
Follow these guidelines when enabling VTP version 2 (v2-mode):
•Toggling the version (v2-mode) state modifies certain parameters of certain default VLANs.
•Each VTP switch automatically detects the capabilities of all the other VTP devices. To use VTP version 2, all VTP switches in the network must support version 2; otherwise, you must configure them to operate in VTP version 1 (no vtp v2-mode).
•If all switches in a domain are VTP version 2-capable, you need only to enable VTP version 2 on one switch; the version number is then propagated to the other version-2 capable switches in the VTP domain.
•If you are using VTP in a Token Ring environment or configuring a Token Ring bridge relay function (TrBRF) or Token Ring concentrator relay function (TrCRF) VLAN media type, VTP version 2 (v2-mode) must be enabled.
•If you are configuring a Token Ring or Token Ring-NET VLAN media type, you must use VTP version 1.
Examples
This example shows how to place the switch in VTP transparent mode:
Switch(vlan)# vtp transparent
Setting device to VTP TRANSPARENT mode.
This example shows how to set the administrative domain for the switch:
Switch(vlan)# vtp domain OurDomainName
Changing VTP domain name from cisco to OurDomainName
This example shows how to configure the VTP domain password:
Switch(vlan)# vtp password private
Setting device VLAN database password to private.
This example shows how to enable pruning in the proposed new VLAN database:
Switch(vlan)# vtp pruning
Pruning switched ON
This example shows how to enable v2 mode in the proposed new VLAN database:
Switch(vlan)# vtp v2-mode
V2 mode enabled.
You can verify your settings by entering the show vtp status privileged EXEC command.
Related Commands
|
|
|
|---|---|
show vtp status |
Displays the VTP statistics for the switch and general information about the VTP management domain status. |
switchport trunk pruning |
Configures the VLAN pruning-eligible list for ports in trunking mode. |
Configures the VTP filename, interface, domain name, and mode. |
Feedback