-
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
show tag-switching tdp discovery
show tag-switching tdp neighbors
show tag-switching tdp parameters
show xtagatm cos-bandwidth-allocation xtagatm
snmp-server enable traps mpls ldp
snmp-server enable traps mpls traffic-eng
snmp-server enable traps mpls vpn
tag-switching atm allocation-mode
tag-switching atm disable-headend-vc
tag-switching request-tags for
show tag-switching tdp discovery
The show tag-switching tdp discovery command is replaced by the show mpls ldp discovery command. See the show mpls ldp discovery command for more information.
show tag-switching tdp neighbors
The show tag-switching tdp neighbors command is replaced by the show mpls ldp neighbors command. See the show mpls ldp neighbor command for more information.
show tag-switching tdp parameters
The show tag-switching tdp parameters command is replaced by the show mpls ldp parameters command. See the show mpls ldp parameters command for more information.
show vlans
To view virtual LAN (VLAN) subinterfaces, use the show vlans command in privileged EXEC mode.
show vlans
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
11.0
This command was introduced.
12.1(3)T
This command was modified to display traffic count on FastEthernet subinterfaces.
Examples
The following is sample output from the show vlans command:
Router# show vlansVirtual LAN ID: 2 (IEEE 802.1Q Encapsulation)vLAN Trunk Interface: FastEthernet5/0.1Protocols Configured: Address: Received: Transmitted:IP 56.0.0.3 16 92129Virtual LAN ID: 3 (IEEE 802.1Q Encapsulation)vLAN Trunk Interface: Ethernet6/0/1.1Protocols Configured: Address: Received: Transmitted:IP 36.0.0.3 1558 1521Virtual LAN ID: 4 (Inter Switch Link Encapsulation)vLAN Trunk Interface: FastEthernet5/0.2Protocols Configured: Address: Received: Transmitted:IP 76.0.0.3 0 7The following is sample output from the show vlans command indicating a native VLAN and a bridged group:
Virtual LAN ID: 1 (IEEE 802.1Q Encapsulation)vLAN Trunk Interface: FastEthernet1/0/2This is configured as native Vlan for the following interface(s) :FastEthernet1/0/2Protocols Configured: Address: Received: Transmitted:Virtual LAN ID: 100 (IEEE 802.1Q Encapsulation)vLAN Trunk Interface: FastEthernet1/0/2.1Protocols Configured: Address: Received: Transmitted:Bridging Bridge Group 1 0 0Table 117 describes the significant fields shown in the display.
show vlan-switch
To display virtual LAN (VLAN) information, use the show vlan-switch command in privileged EXEC mode.
show vlan-switch [brief | id vlan | name name]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Each Ethernet switch port and Ethernet repeater group belongs to only one VLAN. Trunk ports can be on multiple VLANs.
Examples
The following example shows how to display the VLAN parameters for all VLANs within the administrative domain:
Router# show vlan-switchVLAN Name Status Ports---- -------------------------------- --------- -------------------------------1 default active Fa4/0, Fa4/1, Fa4/2, Fa4/3Fa4/4, Fa4/5, Fa4/6, Fa4/7Fa4/8, Fa4/9, Fa4/10, Fa4/11Fa4/12, Fa4/13, Fa4/14, Fa4/15Fa4/16, Fa4/17, Fa4/18, Fa4/19Fa4/20, Fa4/21, Fa4/22, Fa4/23Fa4/24, Fa4/25, Fa4/26, Fa4/27Fa4/28, Fa4/29, Fa4/30, Fa4/31Fa4/32, Fa4/33, Fa4/34, Fa4/35Gi4/0, Gi4/1, Po12 VLAN0002 active3 VLAN0003 active5 VLAN0005 active1002 fddi-default active1003 token-ring-default active1004 fddinet-default active1005 trnet-default activeVLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------1 enet 100001 1500 - - - - - 1002 10032 enet 100002 1500 - - - - - 0 03 enet 100003 1500 - - - - - 0 05 enet 100005 1500 - - - - - 0 01002 fddi 101002 1500 - 0 - - - 1 10031003 tr 101003 1500 1005 0 - - srb 1 10021004 fdnet 101004 1500 - - 1 ibm - 0 01005 trnet 101005 1500 - - 1 ibm - 0 0Table 118 describes the significant fields shown in the display.
show vtp
To display general information about the virtual LAN (VLAN) Trunk Protocol (VTP) management domain, status, and counters, use the show vtp command in privileged EXEC mode.
show vtp {counters | status}
Syntax Description
counters
Displays the VTP counters for the switch.
status
Displays the general information about the VTP management domain.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show vtp counters command:
Router# show vtp countersVTP statistics:Summary advertisements received : 38Subset advertisements received : 0Request advertisements received : 0Summary advertisements transmitted : 13Subset advertisements transmitted : 3Request advertisements transmitted : 0Number of config revision errors : 0Number of config digest errors : 0Number of V1 summary errors : 0VTP pruning statistics:Trunk Join Transmitted Join Received Summary advts received fromnon-pruning-capable device---------------- ---------------- ---------------- ---------------------------Fa0/9 827 824 0Fa0/10 827 823 0Fa0/11 827 823 0Table 119 describes the significant fields shown in the display.
The following is sample output from the show vtp status command:
Router# show vtp statusVTP Version : 2Configuration Revision : 1Maximum VLANs supported locally : 68Number of existing VLANs : 7VTP Operating Mode : ServerVTP Domain Name : test1VTP Pruning Mode : DisabledVTP V2 Mode : DisabledVTP Traps Generation : DisabledMD5 digest : 0x3D 0x02 0xD4 0x3A 0xC4 0x46 0xA1 0x03Configuration last modified by 172.20.130.52 at 3-4-93 22:25:Table 120 describes the significant fields shown in the display.
Related Commands
clear vtp counters
Clears the VTP and pruning counters.
vtp
Configures the VTP mode.
show xtagatm cos-bandwidth-allocation xtagatm
To display information about quality of service (QoS) bandwidth allocation on extended Multiprotocol Label Switching (MPLS) ATM (XTagATM) interfaces, use the show xtagatm cos-bandwidth-allocation xtagatm command in user EXEC or privileged EXEC mode.
show xtagatm cos-bandwidth-allocation xtagatm [xtagatm interface number]
Syntax Description
Defaults
Available 50 percent, control 50 percent.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Use this command to display QoS bandwidth allocation information for the following QoS traffic categories:
•
Available
•
•
•
Examples
The following example shows output from this command:
Router# show xtagatm cos-bandwidth-allocation xtagatm 123CoS Bandwidth allocationavailable 25%standard 25%premium 25%control 25%show xtagatm cross-connect
To display information about the Label Switch Controller (LSC) view of the cross-connect table on the remotely controlled ATM switch, use the show xtagatm cross-connect command in user EXEC or privileged EXEC mode.
show xtagatm cross-connect [traffic] [interface interface [vpi vci] | descriptor descriptor
[vpi vci]]Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
Each connection is listed twice in the output from the show xtagatm cross-connect command, because it shows each interface that is linked by the connection.
The following is sample output from the show xtagatm cross-connect command:
Router# show xtagatm cross-connectPhys Desc VPI/VCI Type X-Phys Desc X-VPI/VCI State10.1.0 1/37 -> 10.3.0 1/35 UP 10.1.0 1/34 -> 10.3.0 1/33 UP 10.1.0 1/33 <-> 10.2.0 0/32 UP 10.1.0 1/32 <-> 10.3.0 0/32 UP 10.1.0 1/35 <- 10.3.0 1/34 UP 10.2.0 1/57 -> 10.3.0 1/49 UP 10.2.0 1/53 -> 10.3.0 1/47 UP 10.2.0 1/48 <- 10.1.0 1/50 UP 10.2.0 0/32 <-> 10.1.0 1/33 UP 10.3.0 1/34 -> 10.1.0 1/35 UP 10.3.0 1/49 <- 10.2.0 1/57 UP 10.3.0 1/47 <- 10.2.0 1/53 UP 10.3.0 1/37 <- 10.1.0 1/38 UP 10.3.0 1/35 <- 10.1.0 1/37 UP 10.3.0 1/33 <- 10.1.0 1/34 UP 10.3.0 0/32 <-> 10.1.0 1/32 UPTable 121 describes the significant fields shown in the display.
The following is sample output from the show xtagatm cross-connect command for a single endpoint:
Router# show xtagatm cross-connect descriptor 10.1.0 1 42Phys desc: 10.1.0Interface: n/aIntf type: switch control portVPI/VCI: 1/42X-Phys desc: 10.2.0X-Interface: XTagATM0X-Intf type: extended tag ATMX-VPI/VCI: 2/38Conn-state: UPConn-type: input/outputCast-type: point-to-pointRx service type: Tag COS 0Rx cell rate: n/aRx peak cell rate: 10000Tx service type: Tag COS 0Tx cell rate: n/aTx peak cell rate: 10000Table 122 describes the significant fields shown in the display.
show xtagatm vc
To display information about terminating virtual circuits (VCs) on extended Multiprotocol Label Switching (MPLS) ATM (XTagATM) interfaces, use the show xtagatm vc command in user EXEC or privileged EXEC mode.
show xtagatm vc [vcd [interface]]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The columns marked VCD, VPI, and VCI display information for the corresponding private VC on the control interface. The private VC connects the XTagATM VC to the external switch. It is termed private because its VPI and VCI are only used for communication between the MPLS LSC and the switch, and it is different from the VPI and VCI seen on the XTagATM interface and the corresponding switch port.
Examples
Each connection is listed twice in the sample output from the show xtagatm vc cross-connect command under each interface that is linked by the connection. Connections are marked as input (unidirectional traffic flow, into the interface), output (unidirectional traffic flow, away from the interface), or in/out (bidirectional).
The following is sample output from the show xtagatm vc command:
Router# show xtagatm vcAAL / Control Interface Interface VCD VPI VCI Type Encapsulation VCD VPI VCI StatusXTagATM0 1 0 32 PVC AAL5-SNAP 2 0 33 ACTIVEXTagATM0 2 1 33 TVC AAL5-MUX 4 0 37 ACTIVEXTagATM0 3 1 34 TVC AAL5-MUX 6 0 39 ACTIVETable 123 describes the significant fields shown in the display.
Related Commands
show atm vc
Displays information about private ATM VCs.
Displays information about remotely connected ATM switches.
snmp-server enable traps mpls ldp
To enable the sending of Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps mpls ldp command in global configuration mode. To disable the sending of MPLS LDP notifications, use the no form of this command.
snmp-server enable traps mpls ldp [session-up | session-down | pv-limit | threshold]
no snmp-server enable traps mpls ldp [session-up | session-down | pv-limit | threshold]
Syntax Description
Defaults
The sending of SNMP notifications is disabled by default.
If you do not specify any of the optional keywords, all four types of LDP notifications are enabled on the LSR.
Command Modes
Global configuration
Command History
12.0(21)ST
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
The MPLS LDP pv-limit (mplsLdpPathVectorLimitMismatch) notification object provides a warning message that can be sent to the NMS when two routers engaged in LDP operations have a dissimilar path vector limit. It is recommended that all LDP-enabled routers in the network be configured with the same path vector limit.
The value of the path vector limit can range from 0 through 255; a value of 0 indicates that loop detection is off; any value other than zero up to 255 indicates that loop detection is on and, in addition, specifies the maximum number of hops through which an LDP message can pass before a loop condition in the network is sensed.
The MPLS LDP threshold (mplsLdpFailedInitSessionThresholdExceeded) notification object provides a warning message that can be sent to a network management station (NMS) when a local LSR and an adjacent LDP peer attempt to set up an LDP session between them, but fail to do so after a specified number of attempts. The default number of attempts is 8. This default value is implemented in Cisco IOS and cannot be changed using either the CLI or an SNMP agent.
In general, Cisco routers support the same features across multiple platforms. Therefore, the most likely incompatibility to occur between Cisco LSRs is a mismatch of their respective ATM VPI/VCI label ranges.
For example, if you specify a range of valid labels for an LSR that does not overlap the range of its adjacent LDP peer, the routers will try eight times to create an LDP session between themselves before the mplsLdpFailedInitSessionThresholdExceeded notification is generated.
Operationally, the LSRs whose label ranges do not overlap continue their attempt to create an LDP session between themselves after the eight retry threshold is exceeded. In such cases, the LDP threshold exceeded notification alerts the network administrator to the existence of a condition in the network that may warrant attention.
RFC 3036, LDP Specification, details the incompatibilities that can exist between Cisco routers and/or other vendor LSRs in an MPLS network. Among such incompatibilities, for example, are the following:
•
•
•
•
The snmp-server enable traps mpls ldp command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples
The following example shows how to enable LDP-specific informs that will be sent to the host myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps mpls ldpRouter(config)# snmp-server host myhost.cisco.com informs version 2c public mpls-ldpsnmp-server enable traps mpls traffic-eng
To enable Multiprotocol Label Switching (MPLS) traffic engineering tunnel state-change Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps mpls traffic-eng command in global configuration mode. To disable MPLS traffic engineering tunnel state-change SNMP notifications, use the no form of this command.
snmp-server enable traps mpls traffic-eng [up | down | reroute]
no snmp-server enable traps mpls traffic-eng [up | down | reroute]
Syntax Description
Defaults
SNMP notifications are disabled by default.
If this command is used without keywords, all available trap types (up, down, reroute) are enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.
This command controls (enables or disables) MPLS traffic engineering tunnel notifications. MPLS Tunnel StateChange notifications, when enabled, will be sent when the connection moves from an "up" to "down" state, when a connection moves from a "down" to "up" state, or when a connection is rerouted.
If you do not specify a specific argument in conjunction with this command, all three types of MPLS traffic engineering tunnel notifications will be sent.
The snmp-server enable traps mpls traffic-eng command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples
The following example shows how to enable the router to send MPLS notifications to the host at the address myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps mpls traffic-engRouter(config)# snmp-server host myhost.cisco.com informs version 2c publicRelated Commands
snmp-server host
Specifies the recipient of an SNMP notification operation.
snmp-server trap-source
Specifies the interface that an SNMP trap should originate from.
snmp-server enable traps mpls vpn
To enable the router to send Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) specific Simple Network Management Protocol (SNMP) notifications (traps and informs), use the snmp-server enable traps mpls vpn command in global configuration mode. To disable MPLS VPN specific SNMP notifications, use the no form of this command.
snmp-server enable traps mpls vpn [vrf-up] [vrf-down] [mid-threshold] [max-threshold] [illegal-label]
no snmp-server enable traps mpls vpn [vrf-up] [vrf-down] [mid-threshold] [max-threshold] [illegal-label]
Syntax Description
Defaults
This command is disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
If this command is used without any of the optional keywords, all MPLS VPN notification types are enabled.
For the vrf-up (mplsVrfIfUp) or vrf-down (mplsVrfIfDown) notifications to be issued from an ATM or Frame Relay subinterface, you must first configure the snmp-server traps atm subif command or the snmp-server traps frame-relay subif command on the subinterfaces, respectively.
The values for mid-threshold and max-threshold are set using the maximum routes limit warn-threshold [warn-only] VRF configuration mode command.
Note
The notification types described above are defined in the following MIB objects of the PPVPN-MPLS-VPN-MIB as follows:
•
•
•
•
•
Examples
The following example shows how to send MPLS VPN trap notifications to the host specified as 172.31.156.34 using the community string named public if a VRF transitions from a down state to an up state or from an up state to a down state:
Router(config)# snmp-server enable traps mpls vpn vrf-up vrf-downRouter(config)# snmp-server host 172.31.156.34 traps public mpls-vpnRelated Commands
spanning-tree cost
To set the path cost of the interface for Spanning Tree Protocol (STP) calculations, use the spanning-tree cost command in interface configuration mode. To revert to the default value, use the no form of this command.
spanning-tree cost cost
no spanning-tree cost
Syntax Description
cost
Path cost; valid values are from 1 to 200000000 for Cisco IOS Releases 12.1(3a)E and later releases and from 1 to 65535 for Cisco IOS releases prior to Cisco IOS Release 12.1(3a)E.
Defaults
The default path cost is computed from the bandwidth setting of the interface; default path costs are:
Ethernet: 100
16-Mb Token Ring: 62
FDDI: 10
FastEthernet: 10
ATM 155: 6
GigibitEthernet: 1
HSSI: 647Command Modes
Interface configuration
Command History
Usage Guidelines
When you specify a value for the cost argument, higher values indicate higher costs. This range applies regardless of the protocol type specified.
Examples
The following example shows how to access an interface and set a path cost value of 250 for the spanning tree VLAN associated with that interface:
Router(config)# interface ethernet 2/0Router(config-if)# spanning-tree cost 250Related Commands
spanning-tree port-priority
To set an interface priority when two bridges tie for position as the root bridge, use the spanning-tree port-priority command in interface configuration mode. To revert to the default value, use the no form of this command.
spanning-tree port-priority port-priority
no spanning-tree port-priority
Syntax Description
Defaults
The port priority is 128.
Command Modes
Interface configuration
Command History
Usage Guidelines
The priority you set breaks the tie.
Examples
The following example shows how to increase the likelihood that the spanning tree instance 20 is chosen as the root-bridge on interface ethernet 2/0:
Router(config)# interface ethernet 2/0Router(config-if)# spanning-tree port-priority 20Router(config-if)#Related Commands
spanning-tree vlan
To configure Spanning Tree Protocol (STP) on a per-virtual LAN (VLAN) basis, use the spanning-tree vlan command in global configuration mode. To return to the default value, use the no form of this command.
spanning-tree vlan vlan-id [forward-time seconds | hello-time seconds | max-age seconds | priority priority | protocol protocol | [root {primary | secondary} [diameter net-diameter [hello-time seconds]]]]
no spanning-tree vlan vlan-id [forward-time | hello-time | max-age | priority | protocol | root]
Syntax Description
Defaults
forward-time: 15 seconds
hello-time: 2 seconds
max-age: 20 seconds
priority: The default with IEEE STP enabled is 32,768; with STP enabled, the default is 128.
protocol: IEEE
root: No STP rootCommand Modes
Global configuration
Command History
Usage Guidelines
When setting the max-age seconds, if a bridge does not hear Bridge Protocol Data Units (BPDU) from the root bridge within the specified interval, it assumes that the network has changed and recomputes the spanning tree topology.
Valid values for protocol are dec (Digital STP), ibm (IBM STP), ieee (IEEE Ethernet STP), and vlan-bridge (VLAN Bridge STP).
The spanning-tree root primary command alters this switch's bridge priority to 8,192. If you enter after spanning-tree root primary command and the switch does not become root, then the bridge priority is changed to 100 less than the bridge priority of the current bridge. If the switch does not become root, an error results.
The spanning-tree root secondary command alters this switch's bridge priority to 16,384. If the root switch should fail, this switch becomes the next root switch.
Use the spanning-tree root commands on backbone switches only.
Examples
The following example shows how to enable spanning tree on VLAN 200:
Router(config)# spanning-tree vlan 200The following example shows how to configure the switch as the root switch for VLAN 10 with a network diameter of 4:
Router(config)# spanning-tree vlan 10 root primary diameter 4The following example shows how to configure the switch as the secondary root switch for VLAN 10 with a network diameter of 4:
Router(config)# spanning-tree vlan 10 root secondary diameter 4Related Commands
tag-control-protocol vsi
To configure the use of Virtual Switch Interface (VSI) on a particular master control port, use the tag-control-protocol vsi command in interface configuration mode. To disable VSI, use the no form of this command.
tag-control-protocol vsi [id controller-id] [base-vc vpi vci] [slaves slave-count] [keepalive timeout] [retry timeout-count] [delay seconds]
no tag-control-protocol vsi [id controller-id] [base-vc vpi vci] [slaves slave-count] [keepalive timeout] [retry timeout-count] [delay seconds]
Syntax Description
Defaults
VSI is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
The command is only available on interfaces that can serve as a VSI master control port. We recommend that all options to the tag-control-protocol vsi command be entered at the same time.
After VSI is active on the control interface (through the earlier issuance of a tag-control-protocol vsi command), reentering the command may cause all associated XTagATM interfaces to shut down and restart. In particular, if you reenter the tag-control-protocol vsi command with any of the following options, the VSI shuts down and reactivates on the control interface:
•
•
•
VSI remains continuously active (that is, the VSI does not shut down and then reactivate) if you reenter the tag-control-protocol vsi command with only one or both of the following options:
•
•
•
In either case, if you reenter the tag-control-protocol vsi command, this causes the specified options to take on the newly specified values; the other options retain their previous values. To restore default values to all the options, enter the no tag-control-protocol command, followed by the tag-control-protocol vsi command.
Examples
The following example shows how to configure the VSI driver on the control interface:
Router(config)# interface atm 0/0Router(config-if)# tag-control-protocol vsi base-vc 0 51tag-switching advertise-tags
The tag-switching advertise-tags command is replaced by the mpls advertise-labels command. See the mpls ldp advertise-labels command for more information.
tag-switching atm allocation-mode
The tag-switching atm allocation-mode command is replaced by the mpls ldp atm control-mode command. See the mpls ldp atm control-mode command for more information.
tag-switching atm cos
The tag-switching atm cos command is replaced by the mpls atm cos command. See the mpls atm cos command for more information.
tag-switching atm disable-headend-vc
The tag-switching atm disable-headend-vc command is replaced by the mpls atm disable-headend-vc command. See the mpls atm disable-headend-vc command for more information.
tag-switching atm maxhops
The tag-switching atm maxhops command is replaced by the mpls ldp maxhops command. See the mpls ldp maxhops command for more information.
tag-switching atm vc-merge
The tag-switching atm vc-merge command is replaced by the mpls atm vc-merge command. See the mpls ldp atm vc-merge command for more information.
tag-switching atm vpi
The tag-switching atm vpi command is replaced by the mpls atm vpi command. See the mpls atm vpi command for more information.
tag-switching atm vp-tunnel
The tag-switching atm vp-tunnel command is replaced by the mpls atm vp-tunnel command. See the mpls atm vp-tunnel command for more information.
tag-switching cos-map
The tag-switching cos-map command is replaced by the mpls cos-map command. See the mpls cos-map command for more information.
tag-switching prefix-map
The tag-switching prefix-map command is replaced by the mpls prefix-map command. See the mpls prefix-map command for more information.
tag-switching request-tags for
The tag-switching request-tags for command is replaced by the mpls request-labels for command. See the mpls request-labels for command for more information.
tag-switching tdp discovery
The tag-switching tdp discovery command is replaced by the mpls ldp discovery command. See the mpls ldp discovery command for more information.
tag-switching tdp holdtime
The tag-switching tdp holdtime command is replaced by the mpls ldp holdtime command. See the mpls ldp holdtime command for more information.
