-
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
mls rp ip multicast management-interface
mpls ip (global configuration)
mpls ip (interface configuration)
mpls ip encapsulate explicit-null
mac-address-table aging-time
To configure the maximum aging time for entries in the Layer 2 table, use the mac-address-table aging-time command in global configuration mode. To reset the seconds value to the default setting, use the no form of this command.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
mac-address-table aging-time seconds
no mac-address-table aging-time seconds
Catalyst Switches
mac-address-table aging-time seconds [vlan vlan-id]
no mac-address-table aging-time seconds [vlan vlan-id]
Syntax Description
Command Default
The system uses a default of 300 seconds for the mac-address-table aging-time when the mac-address-table aging-time command has not been configured.
Command Modes
Global configuration
Command History
Usage Guidelines
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
The aging time entry will take the specified value. Valid entries are from 10 to 1,000,000 seconds.
This command cannot be disabled.
Catalyst Switches
If you do not enter a VLAN, the change is applied to all routed-port VLANs.
Enter 0 seconds to disable aging.
Examples
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
The following example shows the aging time being configured:
Router(config)# mac-address-table aging-time 300Catalyst Switches
The following example shows the aging time being configured:
Router(config)# mac-address-table aging-time 400The following example shows the aging time being disabled:
Router(config)# mac-address-table aging-time 0Related Commands
mac-address-table dynamic
To add dynamic addresses to the MAC address table, use the mac-address-table dynamic command in global configuration mode. Dynamic addresses are automatically added to the address table and dropped from it when they are not in use. To remove dynamic entries from the MAC address table, use the no form of this command.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
mac-address-table dynamic hw-address interface {fa | gi} [slot/port] vlan vlan-id
no mac-address-table dynamic hw-address vlan vlan-id
Catalyst Switches
mac-address-table dynamic hw-address interface [atm slot/port] [vlan vlan-id]
no mac-address-table dynamic hw-address [vlan vlan-id]
Syntax Description
Defaults
Dynamic addresses are not added to the MAC address table.
Command Modes
Global configuration
Command History
Usage Guidelines
If the vlan-id argument is omitted and the no form of the command is used, the MAC address is removed from all VLANs.
Examples
The following example shows how to add a MAC address on port fa1/1 to VLAN 4:
Switch(config)# mac-address-table dynamic 00c0.00a0.03fa fa1/1 vlan 4Related Commands
mac-address-table secure
To add secure addresses to the MAC address table, use the mac-address-table secure command in global configuration mode. To remove secure entries from the MAC address table, use the no form of this command.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
mac-address-table secure hw-address interface {fa | gi} slot/port vlan vlan-id
no mac-address-table secure hw-address vlan vlan-id
Catalyst Switches
mac-address-table secure hw-address interface [atm slot/port] [vlan vlan-id]
no mac-address-table secure hw-address [vlan vlan-id]
Syntax Description
Defaults
Secure addresses are not added to the MAC address table.
Command Modes
Global configuration
Command History
Usage Guidelines
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
Secure addresses can be assigned to only one port at a time. Therefore, if a secure address table entry for the specified MAC address and VLAN already exists on another port, it is removed from that port and assigned to the specified one.
Catalyst Switches
Secure addresses can be assigned only to one port at a time. Therefore, if a secure address table entry for the specified MAC address and VLAN already exists on another port, it is removed from that port and assigned to the specified one.
Dynamic-access ports cannot be configured with secure addresses.
Examples
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
The following example shows how to add a secure MAC address to VLAN 6 of port fa1/1:
Router(config)# mac-address-table secure 00c0.00a0.03fa fa1/1 vlan 6
Catalyst Switches
The following example shows how to add a secure MAC address to VLAN 6 of port fa1/1:
Switch(config)# mac-address-table secure 00c0.00a0.03fa fa1/1 vlan 6The following example shows how to add a secure MAC address to ATM port 2/1:
Switch(config)# mac-address-table secure 00c0.00a0.03fa atm 2/1Related Commands
mac-address-table static
To add static entries to the MAC address table, use the mac-address-table static command in global configuration mode. To remove entries profiled by the combination of specified entry information, use the no form of this command.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
mac-address-table static mac-address {vlan vlan-id} {interface type slot/port}
no mac-address-table static mac-address {vlan vlan-id} {interface type slot/port}
Catalyst Switches
mac-address-table static mac-address {vlan vlan-id} {interface int} [protocol {ip | ipx | assigned}]
no mac-address-table static mac-address {vlan vlan-id} {interface int} [protocol {ip | ipx | assigned}]
Syntax Description
Defaults
Static entries are not added to the MAC address table.
Command Modes
Global configuration
Command History
Usage Guidelines
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
The output interface specified must be a Layer 2 IDB and not an SVI.
Entering the no form of this command does not remove system MAC addresses.
When removing a MAC address, entering the interface type slot/port argument is optional. For unicast entries, the entry is removed automatically. For multicast entries, if you do not specify an interface, the entire entry is removed. You can specify the selected ports to be removed by specifying the interface.
Catalyst Switches
The output interface specified must be a Layer 2 IDB and not an switch virtual interface (SVI).
You can enter up to 15 interfaces per command entered, but you can enter more interfaces by repeating the command.
If you do not enter a protocol type, an entry is automatically created for each of the four protocol types.
Entering the no form of this command does not remove system MAC addresses.
When removing a MAC address, entering the interface type slot/port argument is optional. For unicast entries, the entry is removed automatically. For multicast entries, if you do not specify an interface, the entire entry is removed. You can specify the selected ports to be removed by specifying the interface.
Examples
The following example shows how to add static entries to the MAC address table:
Router(config)# mac-address-table static 0050.3e8d.6400 vlan 100 interface fastethernet5/7Related Commands
show mac-address-table address
Displays MAC address table information for a specific MAC address.
mask destination
To specify the destination mask, use the mask destination command in aggregation cache configuration mode. To disable the destination mask, use the no form of this command.
mask destination minimum value
no mask destination minimum value
Syntax Description
minimum
Configures the minimum value for the mask.
value
Specifies the configurable value for the mask. Range is from 1 to 32.
Defaults
The default value of the minimum mask is zero.
Command Modes
Aggregation cache configuration
Command History
Usage Guidelines
This command is only available with router-based aggregation. Minimum masking capability is not available if router-based aggregation is not enabled.
Examples
The following example shows how to configure the destination-prefix aggregation cache with a minimum mask value:
Router(config)# ip flow-aggregation cache destination-prefixRouter(config-flow-cache)# mask destination minimum 32Related Commands
mask source
To specify the source mask, use the mask source command in aggregation cache configuration mode. To disable the source mask, use the no form of this command.
mask source minimum value
no mask source minimum value
Syntax Description
minimum
Configures the minimum value for the mask.
value
Specifies the configurable value for the mask. Range is from 1 to 32.
Defaults
The default value of the minimum source is zero.
Command Modes
Aggregation cache configuration
Command History
Usage Guidelines
This command is only available with router-based aggregation. Minimum masking capability is not available if router-based aggregation is not enabled.
Examples
The following example shows how to configure the source-prefix aggregation cache with a minimum mask value:
Router(config)# ip flow-aggregation cache source-prefixRouter(config-flow-cache)# mask source minimum 30Related Commands
match mpls-label
To redistribute routes that include Multiprotocol Label Switching (MPLS) labels if the routes meet the conditions specified in the route map, use the match mpls-label command in route map configuration mode. To disable this function, use the no form of this command.
match mpls-label
no match mpls-label
Syntax Description
This command has no arguments or keywords.
Defaults
Routes with MPLS labels are not redistributed.
Command Modes
Route map configuration
Command History
Usage Guidelines
A route map that includes this command can be used in the following instances:
•
With the neighbor route-map in command to manage inbound route maps in BGP
•
Use the route-map global configuration command, and the match and set route map configuration commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria—the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions—the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The match route-map configuration command has multiple formats. The match commands can be given in any order, and all match commands must "pass" to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
When you are passing routes through a route map, a route map can have several parts. Any route that does not match at least one match clause relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want to modify only some data, you must configure a second route map section with an explicit match specified.
Examples
The following example shows how to create a route map that redistributes routes if the following conditions are met:
•
•
Router(config-router)# route-map incoming permit 10Router(config-route-map)# match ip address 2Router(config-route-map)# match mpls-labelRelated Commands
maximum routes
To limit the maximum number of routes in a Virtual Private Network (VPN) routing/forwarding instance (VRF) to prevent a provider edge (PE) router from importing too many routes, use the maximum routes command in VRF configuration submode. To remove the limit on the maximum number of routes allowed, use the no form of this command.
maximum routes limit {warn-threshold | warning-only}
no maximum routes
Syntax Description
Defaults
No limit is set on the maximum number of routes allowed.
Command Modes
VRF configuration
Command History
12.0(7)T
This command was introduced.
12.2(13)T
Support for SNMP notifications was added.
Usage Guidelines
The maximum routes command can be configured in one of two ways:
•
•
To limit the number of routes allowed in the VRF, use the maximum routes limit command with the warn-threshold argument. The warn-threshold argument generates a warning and does not allow the addition of routes to the VRF when the maximum number set by the limit argument is reached. The software generates a warning message everytime a route is added to a VRF when the VRF route count is above the warning threshold. The software also generates a route rejection notification when the maximum threshold is reached and everytime a route is rejected after the limit is reached.
To set a number of routes at which you receive a notification, but which does not limit the number of routes that can be imported into the VRF, use the maximum routes limit command with the warn-only keyword.
To configure the router to generate SNMP notifications (traps or informs) for these values use the snmp-server enable traps mpls vpn global configuration command.
Examples
The following example shows how to set a limit threshold of VRF routes to 1000. When the number of routes for the VRF reaches 1000, the router issues a syslog error message, but continues to accept new VRF routes.
Router(config)# ip vrf vrf1Router(config-vrf)# rd 100:1Router(config-vrf)# route-target import 100:1Router(config-vrf)# maximum routes 1000 warning-onlyThe following example shows how to set the maximum number of VRF routes allowed to 1000 and set the warning threshold at 80 percent of the maximum. When the number of routes for the VRF reaches 800, the router issues a warning message. When the number of routes for the VRF reaches 1000, the router issues a SYSLOG error message and rejects any new routes.
Router(config)# ip vrf vrf2Router(config-vrf)# rd 200:1Router(config-vrf)# route-target import 200:1Router(config-vrf)# maximum routes 1000 80Related Commands
metric-style narrow
To configure a router running Intermediate System-to-Intermediate System (IS-IS) so that it generates and accepts old-style type, length, and value objects (TLVs), use the metric-style narrow command in router configuration mode. To disable this function, use the no form of this command.
metric-style narrow [transition] [level-1 | level-2 | level-1-2]
no metric-style narrow [transition] [level-1 | level-2 | level-1-2]
Syntax Description
Defaults
The Multiprotocol Label Switching (MPLS) traffic engineering image generates only old-style TLVs. To do MPLS traffic engineering, a router must generate new-style TLVs that have wider metric fields.
Command Modes
Router configuration
Command History
Examples
The following example shows how to configure the router to generate and accept old-style TLVs on router level 1:
Router(config-router)# metric-style narrow level-1Related Commands
Configures a router to generate both old-style and new-style TLVs.
Configures a router to generate and accept only new-style TLVs.
metric-style transition
To configure a router running Intermediate System-to-Intermediate System (IS-IS) so that it generates and accepts both old-style and new-style type, length, and value objects (TLVs), use the metric-style transition command in router configuration mode. To disable this function, use the no form of this command.
metric-style transition [level-1 | level-2 | level-1-2]
no metric-style transition [level-1 | level-2 | level-1-2]
Syntax Description
level-1
(Optional) Enables this command on routing level 1.
level-2
(Optional) Enables this command on routing level 2.
level-1-2
(Optional) Enables this command on routing levels 1 and 2.
Defaults
The Multiprotocol Label Switching (MPLS) traffic engineering image generates only old-style TLVs. To do MPLS traffic engineering, a router must generate new-style TLVs that have wider metric fields.
Command Modes
Router configuration
Command History
Examples
The following example shows how to configure a router to generate and accept both old-style and new-style TLVs on router level 2:
Router(config-router)# metric-style transition level-2Related Commands
Configures a router to generate and accept old-style TLVs.
Configures a router to generate and accept only new-style TLVs.
metric-style wide
To configure a router running Intermediate System-to-Intermediate System (IS-IS) so that it generates and accepts only new-style type, length, and value objects (TLVs), use the metric-style wide command in router configuration mode. To disable this function, use the no form of this command.
metric-style wide [transition] [level-1 | level-2 | level-1-2]
no metric-style wide [transition] [level-1 | level-2 | level-1-2]
Syntax Description
Defaults
The Multiprotocol Label Switching (MPLS) traffic engineering image generates only old-style TLVs. To do MPLS traffic engineering, a router must generate new-style TLVs that have wider metric fields.
Command Modes
Router configuration
Command History
Usage Guidelines
If you enter the metric-style wide command, a router generates and accepts only new-style TLVs. Therefore, the router uses less memory and other resources than it would if it generated both old-style and new-style TLVs.
This style is appropriate for enabling MPLS traffic engineering across an entire network.
Note
Examples
The following example shows how to configure a router to generate and accept only new-style TLVs on level 1:
Router(config-router)# metric-style wide level-1Related Commands
Configures a router to generate and accept old-style TLVs.
Configures a router to generate and accept both old-style and new-style TLVs.
mls rp ip
To enable the Multilayer Switching Protocol (MLSP) and Multilayer Switching (MLS), use the mls rp ip command in global configuration mode. To disable MLS, use the no form of this command.
mls rp ip
no mls rp ip
Syntax Description
This command has no arguments or keywords.
Defaults
Multilayer Switching (MLS) is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to enable MLS, either globally or on a specific interface. MLSP is the protocol that runs between the switches and routers.
Examples
The following example enables MLS:
Router(config)# mls rp ipRelated Commands
mls rp ip multicast
To enable IP multicast Multilayer Switching (MLS) (hardware switching) on an external or internal router in conjunction with Layer 3 switching hardware for the Catalyst 5000, use the mls rp ip multicast command in interface configuration mode. To disable IP multicast MLS on the interface or virtual LAN (VLAN), use the no form of this command.
mls rp ip multicast
no mls rp ip multicast
Syntax Description
This command has no arguments or keywords.
Defaults
IP multicast MLS is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is available only on specific router platforms connected to a Catalyst 5000 switch. Use this command to reduce multicast load on the router. The switch performs the multicast packet replication and forwarding.
IP multicast MLS is enabled by default on an interface once IP multicast routing and PIM are enabled.
Examples
The following example shows how to disable IP multicast MLS:
Router(config)# interface fastethernet1/0.1Router(config-if)# no mls rp ip multicastRelated Commands
mls rp ip multicast management-interface
To assign a different interface (other than the default) to act as the management interface for Multilayer Switching (MLS), use the mls rp ip multicast management-interface command in interface configuration mode. To restore the default interface as the management interface, use the no form of this command.
mls rp ip multicast management-interface
no mls rp ip multicast management-interface
Syntax Description
This command has no arguments or keywords.
Defaults
When IP multicast MLS is enabled, the subinterface (or virtual LAN [VLAN] interface) that has the lowest VLAN ID and is active (in the "up" state) is automatically selected as the management interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
When you enable IP multicast MLS, the subinterface (or VLAN interface) that has the lowest VLAN ID and is active (in the "up" state) is automatically selected as the management interface. The one-hop protocol Multilayer Switching Protocol (MLSP) is used between a router and a switch to pass messages about hardware-switched flows. MLSP packets are sent and received on the management interface. Typically, the interface in VLAN 1 is chosen (if that interface exists). Only one management interface is allowed on a single trunk link.
In most cases, we recommend that the management interface be determined by default. However, you can optionally use this command to specify a different router interface or subinterface as the management interface. We recommend using a subinterface with minimal data traffic so that multicast MLSP packets can be sent and received more quickly.
If the user-configured management interface goes down, the router uses the default interface (the active interface with the lowest VLAN ID) until the user-configured interface comes up again.
Examples
The following example shows how to configure the Fast Ethernet interface as the management interface:
Router(config)# interface fastethernet1/0.1Router(config-if)# mls rp ip multicast management-interfaceRelated Commands
Enables IP multicast MLS (hardware switching) on an external or internal router in conjunction with Layer 3 switching hardware for the Catalyst 5000 switch.
mls rp ipx (global)
To enable the router as an IPX Multilayer Switching (MLS) Route Processor (RP), use the mls rp ipx command in global configuration mode. To disable IPX MLS on the router, use the no form of this command.
mls rp ipx
no mls rp ipx
Syntax Description
This command has no arguments or keywords.
Defaults
IPX MLS is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Multilayer Switching Protocol (MLSP) is the protocol that runs between the MLS Switching Engine and the MLS RP.
Examples
The following example enables IPX MLS on the MLS RP:
Router(config)# mls rp ipxRelated Commands
mls rp ipx (interface)
To enable IPX Multilayer Switching (MLS) on a router interface, use the mls rp ipx command in interface configuration mode. To disable IPX MLS on a router interface, use the no form of this command.
mls rp ipx
no mls rp ipx
Syntax Description
This command has no arguments or keywords.
Defaults
IPX MLS is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Multilayer Switching Protocol (MLSP) is the protocol that runs between the MLS Switching Engine and the MLS RP.
Examples
The following example shows how to enable IPX MLS on a router interface:
Router(config-if)# mls rp ipxRelated Commands
mls rp locate ipx
To display information about all switches currently shortcutting for the specified IPX flows, use the mls rp locate ipx command in privileged EXEC mode.
mls rp locate ipx destination-network.destination-node [source-network]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to display the switch that is shortcutting routed flows to the specified IPX flow:
Router# mls rp locate ipx 30.0000.1111.2222locator response from switch id 0010.1400.601fRelated Commands
mls rp management-interface
To specify an interface as the management interface, use the mls rp management-interface command in interface configuration mode. To remove an interface as the management interface, use the no form of this command.
mls rp management-interface
no mls rp management-interface
Syntax Description
This command has no keywords or arguments.
Defaults
No interface is specified as the management interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
Multilayer Switching Protocol (MLSP) packets are sent and received through the management interface.
Select only one IPX Multilayer Switching (MLS) interface connected to the switch. If you fail to select this interface, no connection between the MLS Route Processor (RP) and the MLS Switching Engine occurs, and any routing updates or changes to access lists are not reflected on the switch.
Examples
The following example shows how to select a management interface:
Router(config-if)# mls rp management-interfaceRelated Commands
mls rp nde-address
To specify a NetFlow Data Export (NDE) address, use the mls rp nde-address command in global configuration mode.
mls rp nde-address ip-address
Syntax Description
Defaults
No NDE address is specified.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command on a Route Processor (RP) to specify the NDE address for a router. If you do not specify an NDE IP address for the Multilayer Switching (MLS) RP, the MLS RP automatically selects one of its interface's IP addresses and uses that IP address as its NDE IP address and its MLS IP address.
Examples
The following example shows how to set the NDE address to 172.25.2.1:
Router(config)# mls rp nde-address 172.25.2.1Related Commands
mls rp vlan-id
To assign a virtual LAN (VLAN) identification number to an IPX Multilayer Switching (MLS) interface, use the mls rp vlan-id command in interface configuration mode. To remove a VLAN identification number, use the no form of this command.
mls rp vlan-id vlan-id-number
no mls rp vlan-id vlan-id-number
Syntax Description
Defaults
No VLAN identification number is assigned.
Command Modes
Interface configuration
Command History
Usage Guidelines
The assigned IPX MLS interface must be either an Ethernet or Fast Ethernet interface—both without subinterfaces.
Examples
The following example shows how to assign the VLAN identification number 23 to an IPX MLS interface:
Router(config-if)# mls rp vlan-id 23Related Commands
mls rp vtp-domain
To assign a Multilayer Switching (MLS) interface to a specific Virtual Trunk Protocol (VTP) domain on the MLS Route Processor (RP), use the mls rp vtp-domain command in interface configuration mode. To remove a VTP domain, use the no form of this command.
mls rp vtp-domain domain-name
no mls rp vtp-domain domain-name
Syntax Description
Defaults
The interface is assigned to the null domain.
Command Modes
Interface configuration
Command History
Usage Guidelines
The assigned IPX MLS interface must be either an Ethernet or Fast Ethernet interface—both without subinterfaces.
Examples
The following example shows how to assign the MLS interface to the VTP domain named engineering:
Router(config-if)# mls rp vtp-domain engineeringRelated Commands
monitor session
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
To start a new Switched Port Analyzer (SPAN) session, add or delete interfaces from an existing SPAN session, or delete a SPAN session, use the monitor session command in global configuration mode. To remove one or more source interfaces or destination interfaces from the SPAN session, use the no form of this command.
Source Interface
monitor session session {source {interface type/slot/port}} [, | - | rx | tx | both]
no monitor session session {source {interface type/slot/port}} [, | - | rx | tx | both]
Destination Interface
monitor session session {destination {interface type/slot/port} [, | -]}}
no monitor session session {destination {interface type/slot/port} [, | -]}}
Session
monitor session session
no monitor session session
Catalyst Switches
To start a new SPAN session, add or delete interfaces or VLANs to or from an existing SPAN session, filter SPAN traffic to specific VLANs, or delete a SPAN session, use the monitor session command in global configuration mode. To remove one or more source or destination interfaces from the SPAN session or a source VLAN from the SPAN session, use the no form of this command.
Source Interface or VLAN
monitor session session {source {interface type number} | {vlan vlan-id}} [, | - | rx | tx | both]
no monitor session session {source {interface type number} | {vlan vlan-id}} [, | - | rx | tx | both]
Destination Interface or VLAN
monitor session session {destination {interface type number} [, | -]} | {vlan vlan-id}}
no monitor session session {destination {interface type number} [, | -]} | {vlan vlan-id}}
Filter VLAN
monitor session session {filter {vlan vlan-id} [, | -]}
no monitor session session {filter {vlan vlan-id} [, | -]}
Syntax Description
Defaults
A trunking interface monitors all VLANs and all received and transmitted traffic.
Command Modes
Global configuration
Command History
Usage Guidelines
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
The port-channel number supports six EtherChannels and eight ports in each channel.
Only one SPAN destination for a SPAN session is supported. If you attempt to add another destination interface to a session that already has a destination interface configured, you will get an error. You must first remove a SPAN destination interface before changing the SPAN destination to a different interface.
Catalyst Switches
The number of valid values for port-channel number depends on the software release. For Cisco IOS releases prior to software Release 12.1(3a)E3, valid values are from 1 to 256; for Cisco IOS Release 12.1(3a)E3, 12.1(3a)E4, and 12.1(4)E1, valid values are from 1 to 64. Cisco IOS Release 12.1(5c)EX and later support a maximum of 64 values ranging from 1 to 256.
Only one destination per SPAN session is supported. If you attempt to add another destination interface to a session that already has a destination interface configured, you get an error. You must first remove a SPAN destination interface before changing the SPAN destination to a different interface.
You can configure up to 64 SPAN destination interfaces, but you can have one egress SPAN source interface and up to 64 ingress source interfaces only.
A SPAN session can either monitor VLANs or monitor individual interfaces, but it cannot monitor both specific interfaces and specific VLANs. Configuring a SPAN session with a source interface and then trying to add a source VLAN to the same SPAN session causes an error. Configuring a SPAN session with a source VLAN and then trying to add a source interface to that session also causes an error. You must first clear any sources for a SPAN session before switching to another type of source.
If you enter the filter keyword on a monitored trunk interface, only traffic on the set of specified VLANs is monitored.
Port channel interfaces display in the list of interface options if you have them configured. VLAN interfaces are not supported. However, you can span a particular VLAN by entering the monitor session session source vlan vlan-id command.
Examples
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
The following example shows how to add a destination VLAN to an existing SPAN session:
Router(config)# monitor session 1 destination interface fastEthernet 2/0Catalyst Switches
The following example shows how to add a destination VLAN to an existing SPAN session:
Router(config)# monitor session 1 destination vlan 100The following example shows how to delete a destination VLAN from an existing SPAN session:
Router(config)# no monitor session 1 destination vlan 100The following example shows how to limit SPAN traffic to specific VLANs:
Router(config)# monitor session 1 filter vlan 100 - 304Related Commands
mpls atm control-vc
To configure the control-VC virtual path identifier (VPI) and virtual circuit identifier (VCI) values for the initial link to the Multiprotocol Label Switching (MPLS) peer, use the mpls atm control-vc command in interface configuration mode. To unconfigure the values, use the no form of this command.
mpls atm control-vc vpi vci
no mpls atm control-vc vpi vci
Syntax Description
vpi
Virtual path identifier, in the range from 0 to 4095.
vci
Virtual circuit identifier, in the range from 0 to 65535.
Defaults
0/32
Command Modes
Interface configuration
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
The VPI range of values was extended to 4095.
Usage Guidelines
Use this command to establish the LDP session and to carry non-IP traffic. The default VPI VCI for the control VC is (3, 32). If for any reason you need to have a different control-VC, use the mpls atm control-vc command to configure any VPI VCI allowed by the vpi and vci arguments for the control VC.
Examples
The following example shows how to create an MPLS subinterface on a router and select VPI 1 and VCI 34 as the control VC:
Router(config)# interface atm4/0.1 mplsRouter(config-if)# mpls ipRouter(config-if)# mpls atm control-vc 1 34Related Commands
mpls atm cos
To change the configured bandwidth allocation for class of service (CoS), use the mpls atm cos command in global configuration mode.
mpls atm cos {available | standard | premium | control} weight
Syntax Description
Defaults
Available 50%, control 50%
Command Modes
Global configuration
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Examples
The following example shows how to configure the XTagATM interface for CoS traffic:
Router(config)# interface xtagatm12Router(config-if)# extended-port atm1/0 descriptor 1.2Router(config-if)# mpls ipRouter(config-if)# mpls atm cos available 49Router(config-if)# mpls atm cos standard 50Router(config-if)# mpls atm cos premium 0Router(config-if)# mpls atm cos control 1mpls atm disable-headend-vc
To remove all headend virtual circuits (VCs) from the Multiprotocol Label Switching (MPLS) Label Switch Controller (LSC) and disable its ability to function as an edge label switch router (LSR), use the mpls atm disable-headend-vc command in global configuration mode. To restore the headend VCs of the MPLS LSC and restores full edge LSR functionality, use the no form of this command.
mpls atm disable-headend-vc
no mpls atm disable-headend-vc
Syntax Description
This command has no arguments or keywords.
Defaults
Edge LSR Enabled
Command Modes
Global configuration
Command History
12.0(7)DC
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Usage Guidelines
This command prevents the LSC from initiating headend label VCs (LVCs), and thus reduces the number of LVCs used in the network.
Examples
The following example shows how to disable the MPLS LSC from acting like an edge LSR and therefore cannot create headend LVCs:
mpls atm disable-headend-vcmpls atm multi-vc
To configure a router subinterface to create one or more label virtual circuits (VCs) over which packets of different classes are sent, use the mpls atm multi-vc command in ATM subinterface submode. To remove the label virtual circuits, use the no form of this command.
mpls atm multi-vc
no mpls atm multi-vc
Syntax Description
This command has no arguments or keywords.
Command Modes
ATM subinterface submode
Command History
Usage Guidelines
This command is valid only on ATM MPLS subinterfaces.
Examples
The following example shows how to configure interface ATM2/0/0.1 on the networking device for MPLS quality of service (QoS) multi-VC mode:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface ATM2/0/0.1 mplsRouter(config-subif)# mpls atm multi-vcRouter(config-subif)# exitRouter(config)# exitRelated Commands
mpls atm vpi
To configure the range of values to use in the virtual path identifier (VPI) field for label virtual circuits (LVCs), use the mpls atm vpi command in interface configuration mode. To clear the range of values, use the no form of this command.
mpls atm vpi vpi [- vpi] [vci-range low - high]
no mpls atm vpi vpi [- vpi] [vci-range low - high]
Syntax Description
Defaults
The default VPI range is 1-1.
The default VCI range is 33-65535.
Command Modes
Interface configuration
Command History
Usage Guidelines
You might need to change the default tag virtual path identifier (VPI) range on the switch if:
•
•
To configure ATM MPLS on a router interface (for example, an ATM Interface Processor), you must enable an MPLS subinterface.
Note
Use this command to select an alternate range of VPI values for ATM label assignment on this interface. The two ends of the link negotiate a range defined by the intersection of the range configured at each end.
•
•
•
If you use the vci-range keyword, you must specify a VPI value.
Examples
The following example shows how to create a subinterface and selects a VPI range from VPI 1 to VPI 3:
Router(config)# interface atm4/0.1 mplsRouter(config-if)# mpls ipRouter(config-if)# mpls atm vpi 1-3The following example shows how to create a subinterface with a VPI of 240 and a VCI range between 33 and 4090:
Router(config)# interface atm4/0.1 mplsRouter(config-if)# mpls ipRouter(config-if)# mpls atm vpi 240 vci-range 33-4090Related Commands
mpls atm control-vc
Configures VPI and VCI values for the initial link to an MPLS peer.
mpls atm vp-tunnel
To specify an interface or a subinterface as a virtual path (VP) tunnel, use the mpls atm vp-tunnel command in interface configuration mode. To remove the VP tunnel from an interface or subinterface, use the no form of this command.
mpls atm vp-tunnel vpi [vci-range low - high]
no mpls atm vp-tunnel vpi [vci-range low - high]
Syntax Description
vpi
Virtual path identifier (VPI) value for the local end of the tunnel (0 to 4095).
vci-range low - high
(Optional) Range of virtual channel identifier (VCI) values the VP tunnel can use.
Defaults
If you do not specify a VCI range for the VP tunnel, the tunnel uses the default VCI range of 33-65535.
Command Modes
Interface configuration
Command History
Usage Guidelines
The mpls atm vp-tunnel and mpls atm vpi commands are mutually exclusive.
This command is available on both extended MPLS ATM (XTagATM) interfaces and on LC-ATM subinterfaces of router ATM interfaces. The command is not available on the LS1010, where all subinterfaces are automatically VP tunnels.
It is not necessary to use the mpls atm vp-tunnel command on an XTagATM interface in most applications. The switch learns (through VSI interface discovery) whether the XTagATM interface is a tunnel, the VPI value of the tunnel, and tunnel status.
Examples
The following example shows how to create an MPLS subinterface VP tunnel with a VPI value of 4:
Router(config-if)# mpls atm vp-tunnel 4The following example shows how to create a VP tunnel with a value of 240 and a VCI range of 33 to 4090:
Router(config-if)# mpls atm vp-tunnel 240 vci-range 33-4090mpls cos-map
To create a class map that specifies how classes map to label virtual circuits (VCs) when they are combined with a prefix map, use the mpls cos-map command in global configuration mode.
mpls cos-map cos-map
Syntax Description
Defaults
No class maps are specified.
Command Modes
Global configuration
Command History
Examples
The following example shows how to create a class map:
Router(config)# mpls cos-map 55Router(config-mpls-cos-map)# class 1 premiumRouter(config-mpls-cos-map)# exitRouter(config)#Related Commands
Displays the QoS map used to assign a quantity of label virtual circuits and the associated class of service for those label virtual circuits.
mpls ip (global configuration)
To enable Multiprotocol Label Switching (MPLS) forwarding of IP version 4 (IPv4) packets along normally routed paths for the platform, use the mpls ip command in global configuration mode. To disable MPLS forwarding of IPv4 packets, use the no form of this command.
mpls ip
no mpls ip
Syntax Description
This command has no arguments or keywords.
Defaults
MPLS forwarding of IPv4 packets along normally routed paths is enabled for the platform.
Command Modes
Global configuration
Command History
Usage Guidelines
MPLS forwarding of IPv4 packets along normally routed paths (sometimes called dynamic label switching) is enabled by this command. Enabling MPLS forwarding of IP packets for the platform does not enable it for a platform interface. For a given interface to perform dynamic label switching, this switching function must be enabled for the interface as well as for the platform.
Note
The no form of this command stops dynamic label switching for all platform interfaces, regardless of the interface configuration; it also stops distribution of labels for dynamic label switching. Instead of entering the no mpls ip command individually for each interface, you can stop dynamic label switching on all platform interfaces by entering the command once in global configuration mode. You can then reenable label switching for all platform interfaces by entering an mpls ip command in global configuration mode. (This is commonly known as globally toggling MPLS IP [no mpls ip/mpls ip].)
For a label-controlled ATM (LC-ATM) interface, the no form of this command prevents the establishment of label virtual circuits originating at, terminating at, or passing through the platform.
The no mpls ip command does not affect the sending of labeled packets through label switch path (LSP) tunnels.
Examples
The following example shows how to disable dynamic label switching for the platform and how to terminate all label distribution for the platform:
Router(config)# no mpls ipRelated Commands
Enables MPLS forwarding of IPv4 packets along normally routed paths for a particular interface
mpls ip (interface configuration)
To enable Multiprotocol Label Switching (MPLS) forwarding of IP version 4 (IPv4) packets along normally routed paths for a particular interface, use the mpls ip command in interface configuration mode. To disable MPLS forwarding of IPv4 packets, use the no form of the command.
mpls ip
no mpls ip
Syntax Description
This command has no arguments or keywords.
Defaults
MPLS forwarding of IPv4 packets along normally routed paths is disabled for the interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
MPLS forwarding of IPv4 packets along normally routed paths is sometimes called dynamic label switching. If dynamic label switching is enabled for the platform when this command is issued on an interface, label distribution for the interface begins with the periodic transmission of neighbor Discovery Hello messages on the interface. The mpls ip (interface configuration) command works in conjunction with the mpls ip (global configuration) command to enable label distribution for the platform interface. When the outgoing label for a destination that is routed through the interface is known, packets for the destination are assigned that outgoing label and forwarded through the interface.
Note
The no form of this command causes packets routed out through the interface to be sent unlabeled; this form of the command also terminates label distribution for the interface. However, the no form of the command does not affect the sending of labeled packets through any LSP tunnels that might use the interface.
For a label-controlled ATM (LC-ATM) interface, the no form of this command prevents the establishment of label virtual circuits beginning at, terminating at, or passing through the interface.
Examples
The following example shows how to enable label switching on the specified Ethernet interface:
Router(config)# configure terminalRouter(config-if)# interface Ethernet 0/2Router(config-if)# mpls ipRelated Commands
mpls ip default-route
To enable the distribution of labels associated with the IP default route, use the mpls ip default-route command in global configuration mode.
mpls ip default-route
Syntax Description
This command has no arguments or keywords.
Defaults
No distribution of labels for the IP default route.
Command Modes
Global configuration
Command History
11.1 CT
This command was introduced.
12.1(3)T
This command was modified to reflect new Multiprotocol Label Switching (MPLS) Internet Engineering Task Force (IETF) terminology.
Usage Guidelines
Dynamic label switching (that is, distribution of labels based on routing protocols) must be enabled before you can use the mpls ip default-route command.
Examples
The following example shows how to enable the distribution of labels associated with the IP default route:
Router# configure terminalRouter(config)# mpls ipRouter(config)# mpls ip default-routeRelated Commands
mpls ip encapsulate explicit-null
To encapsulate all packets forwarded from the interface or subinterface with an explicit NULL label header, use the mpls ip encapsulate explicit-null command in interface configuration or subinterface configuration mode. To disable this function, use the no form of this command.
mpls ip encapsulate explicit-null
no mpls ip encapsulate explicit-null
Syntax Description
This command has no arguments or keywords.
Defaults
Packets are sent out without an explicit NULL label header.
Command Modes
Interface configuration
Subinterface configurationCommand History
Usage Guidelines
This is a per-interface command. The command establishes an explicit NULL LSP at the customer edge (CE) router. If MPLS is configured on a router and you enter this command, an error message occurs. This command is also supported on the Cisco 2600 series and Cisco 3600 series platforms.
Examples
The following example shows how to encapsulate all packets forwarded onto the interface or subinterface with an explicit NULL label header:
Router(config-if)# mpls ip encapsulate explicit-null
