Feedback
Table Of Contents
Multiprotocol Label Switching Commands
bgp default route-target filter
clear ip rsvp hello instance counters
clear ip rsvp hello instance statistics
clear ip rsvp hello statistics
clear mpls traffic-eng auto-bw timers
clear mpls traffic-eng auto-tunnel mesh
clear mpls traffic-eng auto-tunnel backup
clear mpls traffic-eng auto-tunnel primary
clear mpls traffic-eng tunnel counters
connect (L2VPN local switching)
Multiprotocol Label Switching Commands
address-family
To enter the address family submode for configuring routing protocols such as Border Gateway Protocol (BGP), Routing Information Protocol (RIP), and static routing, use the address-family command in address family configuration submode. To disable the address family submode for configuring routing protocols, use the no form of this command.
VPN-IPv4 Unicast
address-family vpnv4 [unicast]
no address-family vpnv4 [unicast]
IPv4 Unicast
address-family ipv4 [unicast]
no address-family ipv4 [unicast]
IPv4 Unicast with CE router
address-family ipv4 [unicast] vrf vrf-name
no address-family ipv4 [unicast] vrf vrf-name
Syntax Description
Defaults
Routing information for address family IPv4 is advertised by default when you configure a BGP session using the neighbor remote-as command unless you execute the no bgp default ipv4-activate command.
Command Modes
Address family configuration
Command History
Usage Guidelines
Using the address-family command puts the router in address family configuration submode (prompt: (config-router-af)# ). Within this submode, you can configure address-family specific parameters for routing protocols, such as BGP, that can accommodate multiple Layer 3 address families.
To leave address family configuration submode and return to router configuration mode, enter the exit-address-family or exit command.
Examples
The address-family command in the following example puts the router into address family configuration submode for the VPNv4 address family. Within the submode, you can configure advertisement of Network Layer Reachability Information (NLRI) for the VPNv4 address family using neighbor activate and other related commands:
router bgp 100address-family vpnv4The address-family command in the following example puts the router into address family configuration submode for the IPv4 address family. Use this form of the command, which specifies a VRF, only to configure routing exchanges between provider edge (PE) and customer edge (CE) devices. This address-family command causes subsequent commands entered in the submode to be executed in the context of VRF vrf2. Within the submode, you can use neighbor activate and other related commands to accomplish the following:
•
Configure advertisement of IPv4 NLRI between the PE and CE routers.
•
•
The following example shows how to enter the address family submode:
Router(config)# router bgp 100Router(config-router)# address-family ipv4 unicast vrf vrf2Related Commands
default
Exits from address family submode.
neighbor activate
Enables the exchange of information with a neighboring router.
affinity (LSP Attributes)
To specify attribute flags for links of a label switched path (LSP) in an LSP attribute list, use the affinity command in LSP Attributes configuration mode. To remove the specified attribute flags, use the no form of this command.
affinity value [mask value]
no affinity
Syntax Description
Command Default
Attribute values are not checked.
Command Modes
LSP Attributes configuration (config-lsp-attr)
Command History
Usage Guidelines
Use this command to set the affinity and affinity mask values for an LSP in an LSP attribute list.
The affinity value determines the attribute flags for links that make up the LSP, either 0 or 1. The attribute mask determines which attribute value the router should check. If a bit in the mask is 0, an attribute value of a link or that bit is irrelevant. If a bit in the mask is 1, the attribute value of a link and the required affinity of the LSP for that bit must match.
An LSP can use a link if the link affinity equals the attribute flag value and the affinity mask value.
Any value set to 1 in the affinity should also be set to 1 in the mask.
To associate the LSP affinity attribute and the LSP attribute list with a path option for an LSP, you must configure the tunnel mpls traffic-eng path option command with the attributes string keyword and argument, where string is the identifier for the specific LSP attribute list.
Examples
The following example sets the affinity values for a path option in an LSP attribute list:
configure terminal!mpls traffic-eng lsp attributes 1affinity 0 mask 0exitendRelated Commands
mpls traffic-eng lsp attributes
Creates or modifies an LSP attribute list.
show mpls traffic-eng lsp attributes
Displays global LSP attribute lists.
allocate
To configure local label allocation filters for learned routes for Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP), use the allocate command in MPLS LDP label configuration mode. To remove the specific MPLS LDP local label allocation filter without resetting the LDP session, use the no form of this command.
allocate global {prefix-list {list-name | list-number} | host-routes}
no allocate global {prefix-list {list-name | list-number} | host-routes}
Syntax Description
Command Default
Prefix filters are not configured for MPLS LDP local label allocation.
Command Modes
MPLS LDP label configuration (config-ldp-lbl)
Command History
12.2(33)SRC
This command was introduced.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB.
Usage Guidelines
LDP allocates local labels for all learned routes or prefixes. Use the allocate command to specify a prefix list or a host route to control local label allocation filtering.
If you configure the allocate command with a prefix list as the filter and the prefix list does not exist, a prefix list is created that initially permits all prefixes.
You can configure only one prefix list for the global routing table. Configuring a different prefix list overrides the existing configuration.
If you configure the allocate command with host routes as the filter, then LDP allocates local labels for host routes only.
The no form in a specific allocate command removes that particular local label allocation configuration from the global table.
Examples
The following example shows how to configure a prefix list named List1 found in the global routing table as a filter for MPLS LDP local label allocation:
configure terminal!mpls ldp labelallocate global prefix-list List1endLDP allocates local labels only for prefixes that match the configured prefix list.
The following example shows how to remove a local label allocation filter:
configure terminal!mpls ldp labelno allocate global prefix-list List1endThe following example shows how to configure host routes as the filter for the MPLS LDP local label allocation:
configure terminal!mpls ldp labelallocate global host-routesendLDP allocates local labels only for host routes found in the global routing table.
Related Commands
mpls ldp label
Enters MPLS LDP label configuration mode to specify how MPLS LDP handles local label allocation.
show mpls ldp bindings
Displays the contents of the LIB.
append-after
To insert a path entry after a specified index number, use the append-after command in IP explicit path configuration mode.
append-after index command
Syntax Description
Defaults
No path entry is inserted after a specified index number.
Command Modes
IP explicit path configuration
Command History
Examples
In the following example, the next-address command is inserted after index 5:
Router(config-ip-expl-path)# append-after 5 next-address 10.3.27.3Related Commands
auto-bw (LSP Attributes)
To specify automatic bandwidth configuration for a label switched path (LSP) in an LSP attribute list, use the auto-bw command in LSP Attributes configuration mode. To remove automatic bandwidth configuration, use the no form of this command.
auto-bw [frequency secs] [max-bw kbps] [min-bw kbps] [collect-bw]
no auto-bw
Syntax Description
Command Default
If the command is entered with no optional keywords, automatic bandwidth adjustment for the LSP is enabled, with adjustments made every 24 hours and with no constraints on the bandwidth adjustments made.
If the collect-bw keyword is entered, the bandwidth is sampled but not adjusted, and the other options, if any, are ignored.
If the collect-bw keyword is not entered and some, but not all of the other keywords are entered, the defaults for the keywords not entered are: frequency, every 24 hours; min-bw, unconstrained (0); max-bw, unconstrained.Command Modes
LSP Attributes configuration (config-lsp-attr)
Command History
Usage Guidelines
Use this command to set an automatic bandwidth configuration in an LSP attributes list.
To sample the bandwidth used by an LSP without automatically adjusting it, specify the collect-bw keyword in the auto-bw command in an LSP attribute list.
If you enter the auto-bw command without the collect-bw keyword, the bandwidth of the LSP is adjusted to the largest average output rate sampled for the LSP since the last bandwidth adjustment for the LSP was made.
To constrain the bandwidth adjustment that can be made to an LSP in an LSP attribute list, use the max-bw or min-bw keyword and specify the permitted maximum allowable bandwidth or minimum allowable bandwidth, respectively.
The no form of the auto-bw command disables bandwidth adjustment for the tunnel and restores the configured bandwidth for the LSP where configured bandwidth is determined as follows:
•
•
To associate the LSP automatic bandwidth adjustment attribute and the LSP attribute list with a path option for an LSP, you must configure the tunnel mpls traffic-eng path option command with the attributes string keyword and argument, where string is the identifier for the specific LSP attribute list.
Examples
The following example sets automatic bandwidth configuration for an LSP in an LSP attribute list:
configure terminal!mpls traffic-eng lsp attributes 1auto-bwexitendRelated Commands
mpls traffic-eng lsp attributes
Creates or modifies an LSP attribute list.
show mpls traffic-eng lsp attributes
Displays global LSP attribute lists.
bandwidth (LSP Attributes)
To configure label switched path (LSP) bandwidth in an LSP attribute list, use the bandwidth command in LSP Attributes configuration mode. To remove the configured bandwidth from the LSP attribute list, use the no form of this command.
bandwidth [sub-pool | global] kbps
no bandwidth
Syntax Description
Command Default
The default bandwidth is 0.
Command Modes
LSP Attributes configuration (config-lsp-attr)
Command History
Usage Guidelines
Use this command to configure LSP bandwidth in the LSP attribute list. The bandwidth configured can be associated with both dynamic and explicit path options.
To associate the LSP bandwidth and the LSP attribute list with a path option for an LSP, you must configure the tunnel mpls traffic-eng path option command with the attributes string keyword and argument, where string is the identifier for the specific LSP attribute list.
The bandwidth configured in the LSP attribute list will override the bandwidth configured on the tunnel.
Examples
The following example shows how to set the LSP bandwidth to 5000 kbps in the LSP attribute list identified with the numeral 2:
configure terminal!mpls traffic-eng lsp attributes 2bandwidth 5000exitendRelated Commands
mpls traffic-eng lsp attributes
Creates or modifies an LSP attribute list.
show mpls traffic-eng lsp attributes
Displays global LSP attribute lists.
bgp default route-target filter
To enable automatic Border Gateway Protocol (BGP) default route-target community filtering, use the bgp default route-target filter command in router configuration mode. To disable automatic BGP route-target community filtering or to enable pseudowire switching in address family configuration mode, use the no form of this command.
bgp default route-target filter
no bgp default route-target filter
Syntax Description
This command has no arguments or keywords.
Command Default
Automatic BGP default route-target community filtering is enabled.
Command Modes
Router configuration (config-router)
Address family configuration (config-router-af)Command History
Usage Guidelines
Use the bgp default route-target filter command to control the distribution of VPN routing information through the list of VPN route-target communities.
When you use the no form of this command, all received VPN-IPv4 routes are accepted by the configured router. Accepting VPN-IPv4 routes is the desired behavior for a router configured as an ASBR or as a customer edge (CE) BGP border edge router.
If you configure the router for BGP route-target community filtering, all received exterior BGP (EBGP) VPN-IPv4 routes are discarded when those routes do not contain a route-target community value that matches the import list of any configured VPN routing and forwarding (VRF) instances. This is the desired behavior for a router configured as a provider edge (PE) router.
Note
Enabling Pseudowire Switching at the ASBR
In Cisco IOS Release 15.1(1)S, the functionality of the no form of the bgp default route-target filter command has been modified to support Virtual Private LAN Switching (VPLS) on an ASBR.
In router family configuration mode (router-config-af), which is entered by using the address-family l2vpn command, the no bgp default route-target filter command enables pseudowire switching.
Examples
In the following example, BGP route-target filtering is disabled for autonomous system 120:
router bgp 120no bgp default route-target filterPseudowire Switching Enabled at the ASBR
In the following example, pseudowire switching is enabled at the ASBR:
Router# enableRouter# configure terminalRouter(config)# router bgp 1Router(config-router)# address-family l2vpnRouter(config-router-af)# no bgp default route-target filterRelated Commands
address-family l2vpn
Enters address family configuration mode to configure a routing session using L2VPN endpoint provisioning address information.
bgp next-hop
To configure a loopback interface as the next hop for routes associated with a VPN routing and forwarding instance (VRF), use the bgp next-hop command in VRF configuration mode. To return the router to default operation, use the no form of this command.
bgp next-hop loopback number
no bgp next-hop
Syntax Description
loopback number
Specifies the number of the loopback interface. The value that can be entered for this argument is a number from 1 to 2147483647.
Defaults
The IP address of the source interface, from which the route was advertised is set as the next hop when this command is not enabled.
Command Modes
VRF configuration
Command History
Usage Guidelines
The bgp next-hop command is used in Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) and Tunnel Engineering (TE) configurations. This command allows you to configure a loopback interface as the next hop for routes that are associated with the specified VRF. This command can be used, for example, to configure VPN traffic to use a specific Label Switched Path (LSP) through an MPLS core network.
Examples
In the following example, loopback interface 0 is configured as the next hop for VPN traffic associated with VRF RED:
Router(config)# ip vrf REDRouter(config-vrf)# rd 40000:1Router(config-vrf)# route-target import 40000:2Router(config-vrf)# route-target export 40000:2Router(config-vrf)# bgp next-hop loopback 0Related Commands
ip vrf
Configures a VRF routing table.
show ip vrf
Displays the set of defined VRFs and associated interfaces.
bgp scan-time
To configure scanning intervals of Border Gateway Protocol (BGP) routers for next hop validation or to decrease import processing time of Virtual Private Network version 4 (VPNv4) routing information, use the bgp scan-time command in address family or router configuration mode. To return the scanning interval of a router to its default scanning interval of 60 seconds, use the no form of this command.
bgp scan-time [import] scanner-interval
no bgp scan-time [import] scanner-interval
Syntax Description
Command Default
The default scanning interval is 60 seconds.
Command Modes
Address family configuration (config-router-af)
Router configuration (config-router)Command History
Usage Guidelines
Entering the no form of this command does not disable scanning, but removes it from the output of the show running-config command.
The import keyword is supported in address family VPNv4 unicast mode only.
The BGP Event Based VPN Import feature introduced a modification to the existing BGP path import process using new commands and the import keyword was removed from the bgp scan-time command in Cisco IOS Release 15.0(1)M, 12.2(33)SRE, and later releases.
Examples
In the following router configuration example, the scanning interval for next hop validation of IPv4 unicast routes for BGP routing tables is set to 20 seconds:
router bgp 100no synchronizationbgp scan-time 20In the following address family configuration example, the scanning interval for next hop validation of address family VPNv4 unicast routes for BGP routing tables is set to 45 seconds:
router bgp 150address-family vpn4 unicastbgp scan-time 45In the following address family configuration example, the scanning interval for importing address family VPNv4 routes into IP routing tables is set to 30 seconds:
router bgp 150address-family vpnv4 unicastbgp scan-time import 30Related Commands
cell-packing
To enable ATM over Multiprotocol Label Switching (MPLS) or Layer 2 Tunneling Protocol Version 3 (L2TPv3) to pack multiple ATM cells into each MPLS or L2TPv3 packet, use the cell-packing command in the appropriate configuration mode. To disable cell packing, use the no form of this command.
cell-packing [cells] [mcpt-timer timer]
no cell-packing
Syntax Description
Command Default
Cell packing is disabled.
Command Modes
Interface configuration
L2transport VC configuration—for ATM VC
L2transport VP configuration—for ATM VP
VC class configurationCommand History
Usage Guidelines
The cell-packing command is available only if you configure the ATM VC or virtual path (VP) with ATM adaptation layer 0 (AAL0) encapsulation. If you specify ATM adaptation layer 5 (AAL5) encapsulation, the command is not valid.
Only cells from the same VC or VP can be packed into one MPLS or L2TPv3 packet. Cells from different connections cannot be concatenated into the same packet.
When you change, enable, or disable the cell-packing attributes, the ATM VC or VP and the MPLS or L2TPv3 emulated VC are reestablished.
If a provider edge (PE) router does not support cell packing, the PE router sends only one cell per MPLS or L2TPv3 packet.
The number of packed cells need not match between the PE routers. The two PE routers agree on the lower of the two values. For example, if PE1 is allowed to pack 10 cells per MPLS or L2TPv3 packet and PE2 is allowed to pack 20 cells per MPLS or L2TPv3 packet, the two PE routers would agree to send no more than 10 cells per packet.
If the number of cells packed by the peer PE router exceeds the limit, the packet is dropped.
If you issue the cell-packing command without first specifying the atm mcpt-timers command, you get the following error:
Please set mcpt values firstIn order to support cell packing for static pseudowires, both PEs must run Cisco IOS Release 12.2(1)SRE, and the maximum number of cells that can be packed must be set to the same value on each.
Examples
The following example shows cell packing enabled on an interface set up for VP mode. The cell-packing command specifies that ten ATM cells be packed into each MPLS packet. The command also specifies that the second maximum cell-packing timeout (MCPT) timer be used.
Router> enableRouter# configure terminalRouter(config)# interface atm1/0Router(config-if)# atm mcpt-timers 1000 800 500Router(config-if)# atm pvp 100 l2transportRouter(config-if-atm-l2trans-pvp)# xconnect 10.0.0.1 234 encapsulation mplsRouter(config-if-atm-l2trans-pvp)# cell-packing 10 mcpt-timer 2The following example configures ATM cell relay over MPLS with cell packing in VC class configuration mode. The VC class is then applied to an interface.
Router> enableRouter# configure terminalRouter(config)# vc-class atm cellpackingRouter(config-vc-class)# encapsulation aal0Router(config-vc-class)# cell-packing 10 mcpt-timer 1Router(config-vc-class)# exitRouter(config)# interface atm1/0Router(config-if)# atm mcpt-timers 100 200 250Router(config-if)# class-int cellpackingRouter(config-if)# pvc 1/200 l2transportRouter(config-if-atm-l2trans-pvc)# xconnect 10.13.13.13 100 encapsulation mplsThe following example configures ATM AAL5 over L2TPv3 in VC class configuration mode. The VC class is then applied to an interface.
Router(config)# vc-class atm aal5classRouter(config-vc-class)# encapsulation aal5!Router(config)# interface atm1/0Router(config-if)# class-int aal5classRouter(config-if)# pvc 1/200 l2transportRouter(config-if-atm-l2trans-pvc)# xconnect 10.13.13.13 100 encapsulation l2tpv3Related Commands
class (MPLS)
To configure a defined Multiprotocol Label Switching (MPLS) class of service (CoS) map that specifies how classes map to label switched controlled virtual circuits (LVCs) when combined with a prefix map, use the class command in CoS map submode. To remove the defined MPLS CoS map, use the no form of this command.
class class [available | standard | premium | control]
no class class [available | standard | premium | control]
Syntax Description
Defaults
This command is disabled.
Command Modes
CoS map submode
Command History
Examples
The following example shows how to configure a CoS map:
Router(config)# mpls cos-map 55Router(config-mpls-cos-map)# class 1 premiumRouter(config-mpls-cos-map)# exitRelated Commands
clear ip route vrf
To remove routes from the Virtual Private Network (VPN) routing and forwarding(VRF) table, use the clear ip route vrf command in user EXEC or privileged EXEC mode.
clear ip route vrf vrf-name {* | network [mask]}
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Use this command to clear routes from the routing table. Use the asterisk (*) to delete all routes from the forwarding table for a specified VRF, or enter the address and mask of a particular network to delete the route to that network.
Examples
The following command shows how to remove the route to the network 10.13.0.0 in the vpn1 routing table:
Router# clear ip route vrf vpn1 10.13.0.0Related Commands
clear ip rsvp hello bfd
To globally reset to zero the number of times that the Bidirectional Forwarding Detection (BFD) protocol was dropped on an interface or the number of times that a link was down, use the clear ip rsvp hello bfd command in user EXEC or privileged EXEC mode. To disable the resetting of those counters, use the no form of this command.
clear ip rsvp hello bfd {lost-cnt | nbr-lost}
no clear ip rsvp hello bfd {lost-cnt | nbr-lost}
Syntax Description
lost-cnt
Resets to zero the number of times that the BFD session was lost (dropped) on an interface.
nbr-lost
Resets to zero the number of times the BFD protocol detected that a link was down.
Command Default
The counters are not reset to zero.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
When you unconfigure BFD-triggered Fast Reroute, the BFD session is not torn down. Enter the clear ip rsvp hello bfd command to clear show command output for Multiprotocol Label Switching (MPLS) traffic engineering (TE) features that use the BFD protocol.
The clear ip rsvp hello bfd command globally resets to zero the LostCnt field in the show ip rsvp hello bfd nbr summary command and the show ip rsvp hello bfd nbr command. Those fields show the number of times that the BFD session was lost (dropped) on an interface.
The clear ip rsvp hello bfd command also resets to zero the Communication with neighbor lost field in the show ip rsvp hello bfd nbr detail command. That field shows the number of times the BFD protocol detected that a link was down.
Examples
The following example resets to zero the Communication with neighbor lost field in the show ip rsvp hello bfd nbr detail command that shows the number of times the BFD protocol detected that a link was down:
Router# clear ip rsvp hello bfd nbr-lostRelated Commands
clear ip rsvp hello instance counters
To clear (refresh) the values for Hello instance counters, use the clear ip rsvp hello instance counters command in privileged EXEC mode.
clear ip rsvp hello instance counters
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Privileged EXEC
Command History
Examples
Following is sample output from the show ip rsvp hello instance detail command and then the clear ip rsvp hello instance counters command. Notice that the "Statistics" fields have been cleared to zero.
Router# show ip rsvp hello instance detailNeighbor 10.0.0.2 Source 10.0.0.1State: UP (for 2d18h)Type: PASSIVE (responding to requests)I/F: Et1/1LSPs protecting: 0Refresh Interval (msec) (used when ACTIVE)Configured: 100Statistics: (from 2398195 samples)Min: 100Max: 132Average: 100Waverage: 100 (Weight = 0.8)Current: 100Src_instance 0xA9F07C13, Dst_instance 0x9BBAA407Counters:Communication with neighbor lost:Num times: 0Reasons:Missed acks: 0Bad Src_Inst received: 0Bad Dst_Inst received: 0I/F went down: 0Neighbor disabled Hello: 0Msgs Received: 2398194Sent: 2398195Suppressed: 0Router# clear ip rsvp hello instance countersNeighbor 10.0.0.2 Source 10.0.0.1State: UP (for 2d18h)Type: PASSIVE (responding to requests)I/F: Et1/1LSPs protecting: 0Refresh Interval (msec) (used when ACTIVE)Configured: 100Statistics:Min: 0Max: 0Average: 0Waverage: 0Current: 0Src_instance 0xA9F07C13, Dst_instance 0x9BBAA407Counters:Communication with neighbor lost:Num times: 0Reasons:Missed acks: 0Bad Src_Inst received: 0Bad Dst_Inst received: 0I/F went down: 0Neighbor disabled Hello: 0Msgs Received: 2398194Sent: 2398195Suppressed: 0Related Commands
clear ip rsvp hello instance statistics
To clear Hello statistics for an instance, use the clear ip rsvp hello instance statistics command in privileged EXEC mode.
clear ip rsvp hello instance statistics
Syntax Description
This command has no arguments or keywords.
Command Default
Hello statistics are not cleared for an instance.
Command Modes
Privileged EXEC
Command History
Examples
This example shows sample output from the show ip rsvp hello statistics command and the values in those fields after you enter the clear ip rsvp hello instance statistics command.
Router# show ip rsvp hello statisticsStatus: EnabledPacket arrival queue:Wait times (msec)Current:0Average:0Weighted Average:0 (weight = 0.8)Max:4Current length: 0 (max:500)Number of samples taken: 2398525Router# clear ip rsvp hello instance statisticsStatus: EnabledPacket arrival queue:Wait times (msec)Current:0Average:0Weighted Average:0 (weight = 0.8)Max:0Current length: 0 (max:500)Number of samples taken: 0Related Commands
clear ip rsvp hello statistics
To globally clear Hello statistics, use the clear ip rsvp hello statistics command in privileged EXEC mode.
clear ip rsvp hello statistics
Syntax Description
This command has no arguments or keywords.
Command Default
Hello statistics are not globally cleared.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to remove all information about how long Hello packets have been in the Hello input queue.
Examples
Following is sample output from the show ip rsvp hello statistics command and the clear ip rsvp hello statistics command. Notice that the values in the "Packet arrival queue" fields have been cleared.
Router# show ip rsvp hello statisticsStatus: EnabledPacket arrival queue:Wait times (msec)Current:0Average:0Weighted Average:0 (weight = 0.8)Max:4Current length: 0 (max:500)Number of samples taken: 2398525Router# clear ip rsvp hello statisticsStatus: EnabledPacket arrival queue:Wait times (msec)Current:0Average:0Weighted Average:0 (weight = 0.8)Max:0Current length: 0 (max:500)Number of samples taken: 16Related Commands
ip rsvp signalling hello statistics
Enables Hello statistics on the router.
show ip rsvp hello statistics
Displays how long Hello packets have been in the Hello input queue.
clear ip rsvp msg-pacing
To clear the Resource Reservation Protocol (RSVP) message pacing output from the show ip rsvp neighbor command, use the clear ip rsvp msg-pacing command in privileged EXEC mode.
clear ip rsvp msg-pacing
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example clears the RSVP message pacing output:
Router# clear ip rsvp msg-pacingRelated Commands
clear mpls counters
To clear the Multiprotocol Label Switching (MPLS) forwarding table disposition counters, the Any Transport over MPLS (AToM) imposition and disposition virtual circuit (VC) counters, and the MAC address withdrawal counters, use the clear mpls counters command in privileged EXEC mode.
clear mpls counters
Syntax Description
This command has no arguments or keywords.
Defaults
Checkpoint information resides on the active and standby Route Processor.
Command Modes
Privileged EXEC
Command History
Examples
In the following example, the first show mpls forwarding-table command shows that 590 label-switched bytes exist in the forwarding table. The clear mpls counters command clears the counters. The second show mpls forwarding-table command shows that the number of label-switched bytes is 0.
Router# show mpls forwarding-tableLocal Outgoing Prefix Bytes Label Outgoing Next HopLabel Label or VC or Tunnel Id Switched interface20 30 10.10.17.17 590 Et3/0 172.16.0.2Router# clear mpls countersClear "show mpls forwarding-table" counters [confirm]mpls forward counters clearedRouter# show mpls forwarding-tableLocal Outgoing Prefix Bytes Label Outgoing Next HopLabel Label or VC or Tunnel Id Switched interface20 30 10.10.17.17 0 Et3/0 172.16.0.2In the following example, the first show mpls l2transport vc detail command shows that one MAC address withdrawal message was sent (and none were received), 15 packets were received and sent, 1656 bytes were received, and 1986 bytes were sent. The clear mpls counters command clears the counters. The second show mpls l2transport vc detail command shows that no MAC address withdrawal messages, bytes, or packets were received or sent. (If there are no MAC address withdrawal messages received or sent, the MAC Withdraw field is absent.)
Router# show mpls l2transport vc detailLocal interface: Et1/0 up, line protocol up, Ethernet upDestination address: 12.1.1.1, VC ID: 99, VC status: upOutput interface: Se2/0, imposed label stack {21 16}Preferred path: not configuredDefault path: activeNext hop: point2pointCreate time: 00:00:32, last status change time: 00:00:14Signaling protocol: LDP, peer 12.1.1.1:0 upTargeted Hello: 11.1.1.1(LDP Id) -> 12.1.1.1Status TLV support (local/remote) : enabled/supportedLabel/status state machine : established, LruRruLast local dataplane status rcvd: no faultLast local SSS circuit status rcvd: no faultLast local SSS circuit status sent: no faultLast local LDP TLV status sent: no faultLast remote LDP TLV status rcvd: no faultMPLS VC labels: local 23, remote 16Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:MAC Withdraw: sent:1, received:0 <---- MAC address withdrawal totalsSequencing: receive disabled, send disabledSSO Descriptor: 12.1.1.1/99, local label: 23SSM segment/switch IDs: 16387/8193 (used), PWID: 8193VC statistics:packet totals: receive 15, send 15 <---- packet totalsbyte totals: receive 1656, send 1986 <---- byte totalspacket drops: receive 0, seq error 0, send 0Router# clear mpls countersClear "show mpls forwarding-table" counters [confirm]mpls forward counters clearedRouter# show mpls l2transport vc detailLocal interface: Et1/0 up, line protocol up, Ethernet upDestination address: 12.1.1.1, VC ID: 99, VC status: upOutput interface: Se2/0, imposed label stack {21 16}Preferred path: not configuredDefault path: activeNext hop: point2pointCreate time: 00:00:32, last status change time: 00:00:14Signaling protocol: LDP, peer 12.1.1.1:0 upTargeted Hello: 11.1.1.1(LDP Id) -> 12.1.1.1Status TLV support (local/remote) : enabled/supportedLabel/status state machine : established, LruRruLast local dataplane status rcvd: no faultLast local SSS circuit status rcvd: no faultLast local SSS circuit status sent: no faultLast local LDP TLV status sent: no faultLast remote LDP TLV status rcvd: no faultMPLS VC labels: local 23, remote 16Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabledSSO Descriptor: 12.1.1.1/99, local label: 23SSM segment/switch IDs: 16387/8193 (used), PWID: 8193VC statistics:packet totals: receive 0, send 0 <---- packet totalsbyte totals: receive 0, send 0 <---- byte totalspacket drops: receive 0, seq error 0, send 0Related Commands
show mpls forwarding-table
Displays the contents of the MPLS FIB.
show mpls l2transport vc detail
Displays detailed information related to a VC.
clear mpls ip iprm counters
To clear the IP Rewrite Manager (IPRM) counters, use the clear mpls ip iprm counters command in privileged EXEC mode.
clear mpls ip iprm counters
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command sets IPRM counters to zero.
Examples
The command in the following example clears the IPRM counters:
Router# clear mpls ip iprm countersClear iprm counters [confirm]Related Commands
clear mpls ldp checkpoint
To clear the checkpoint information from the Label Information Base (LIB) entries on the active Route Processor (RP) or PRE and to clear the LIB entries created by checkpointing on the standby RP or PRE, use the clear mpls ldp checkpoint command in privileged EXEC mode.
clear mpls ldp checkpoint [vrf vpn-name] {network {mask | length} [longer-prefixes] | *} [incomplete]
Cisco 10000 Series Routers
clear mpls ldp checkpoint {network {mask | length} [longer-prefixes] | *} [incomplete]
Syntax Description
Defaults
Checkpoint information resides on the active and standby RP.
Command Modes
Privileged EXEC
Command History
12.2(25)S
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers.
Usage Guidelines
Use this command only when Cisco support personnel recommend it as a means of rectifying a problem.
On the active RP or PRE, this command does the following:
•
•
On the standby RP or PRE, this command deletes all of the LIB entries created by checkpointing.
Examples
The command in the following example clears the checkpointing information for prefix 10.1.10.1:
Router(config)# clear mpls ldp checkpoint 10.1.10.1 32Clear LDP bindings checkpoint state [confirm]00:20:29: %LDP-5-CLEAR_CHKPT: Clear LDP bindings checkpoint state (*) by consoleRelated Commands
show mpls ldp checkpoint
Displays information about the LDP checkpoint system on the active RP.
clear mpls ldp neighbor
To forcibly reset a label distribution protocol (LDP) session, use the clear mpls ldp neighbor command in privileged EXEC mode.
clear mpls ldp neighbor [vrf vpn-name] {nbr-address | *}
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The clear mpls ldp neighbor command terminates the specified LDP sessions. The LDP sessions should be reestablished if the LDP configuration remains unchanged.
You can clear an LDP session for an interface-specific label space of an LSR by issuing the no mpls ip command and then the mpls ip command on the interface associated with the LDP session.
Examples
The following example resets an LDP session:
Router# clear mpls ldp neighbor 10.12.12.12To verify the results of the clear mpls ldp neighbor command, enter the show mpls ldp neighbor command. Notice the value in the "Up time" field.
Router# show mpls ldp neighbor 10.12.12.12Peer LDP Ident: 10.12.12.12:0; Local LDP Ident 10.13.13.13:0TCP connection: 10.12.12.12.646 - 10.13.13.13.15093State: Oper; Msgs sent/rcvd: 142/138; DownstreamUp time: 02:16:28LDP discovery sources:Serial1/0, Src IP addr: 10.0.0.2Addresses bound to peer LDP Ident:10.0.0.129 10.12.12.12 10.0.0.2 10.1.0.510.7.0.1Then enter the following clear mpls ldp neighbor 12.12.12.12 command. With mpls ldp logging configured, the easiest way to verify the clear mpls ldp neighbor command is to monitor the LDP log messages.
Router# clear mpls ldp neighbor 10.12.12.121w1d: %LDP-5-CLEAR_NBRS: Clear LDP neighbors (10.12.12.12) by console1w1d: %LDP-5-NBRCHG: LDP Neighbor 10.12.12.12:0 is DOWN1w1d: %LDP-5-NBRCHG: LDP Neighbor 10.12.12.12:0 is UPReenter the show mpls ldp neighbor 10.12.12.12 command. Notice that the "Up time" value has been reset.
Router# show mpls ldp neighbor 10.12.12.12Peer LDP Ident: 10.12.12.12:0; Local LDP Ident 10.13.13.13:0TCP connection: 10.12.12.12.646 - 10.13.13.13.15095State: Oper; Msgs sent/rcvd: 125/121; DownstreamUp time: 00:00:05LDP discovery sources:Serial1/0, Src IP addr: 10.0.0.2Addresses bound to peer LDP Ident:10.0.0.129 10.12.12.12 10.0.0.2 10.1.0.510.7.0.1The following example resets all LDP sessions:
Router# clear mpls ldp neighbor *Related Commands
clear mpls traffic-eng auto-bw timers
To reinitialize the automatic bandwidth adjustment feature on a platform, use the clear mpls traffic-eng auto-bw timers command in user EXEC mode.
clear mpls traffic-eng auto-bw timers
Syntax Description
This command has no arguments or keywords.
Defaults
There are no defaults for this command.
Command Modes
User EXEC
Command History
Usage Guidelines
For each tunnel for which automatic bandwidth adjustment is enabled, the platform maintains information about sampled output rates and the time remaining until the next bandwidth adjustment. The clear mpls traffic-eng auto-bw timers command clears this information for all such tunnels. The effect is as if automatic bandwidth adjustment had just been enabled for the tunnels.
Examples
The following example shows how to clear information about sampled output rates and the time remaining until the next bandwidth adjustment:
Router# clear mpls traffic-eng auto-bw timersClear mpls traffic engineering auto-bw timers [confirm]Related Commands
clear mpls traffic-eng auto-tunnel mesh
To remove all mesh tunnel interfaces and re-create them, use the clear mpls traffic-eng auto-tunnel mesh command in privileged EXEC mode.
clear mpls traffic-eng auto-tunnel mesh
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example shows how to remove all mesh tunnel interfaces and re-create them:
Router# clear mpls traffic-eng auto-tunnel meshRelated Commands
clear mpls traffic-eng auto-tunnel backup
To remove all the backup autotunnels and re-create them, use the clear mpls traffic-eng auto-tunnel backup command in global configuration mode.
clear mpls traffic-eng auto-tunnel backup
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Examples
The following example removes all backup autotunnels and re-creates them:
Router# clear mpls traffic-eng auto-tunnel backupRelated Commands
show ip rsvp fast-reroute
Displays information about fast reroutable primary tunnels and their corresponding backup tunnels that provide protection.
clear mpls traffic-eng auto-tunnel primary
To remove all the primary autotunnels and re-create them, use the clear mpls traffic-eng auto-tunnel primary command in global configuration mode.
clear mpls traffic-eng auto-tunnel primary
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Global configuration
Command History
Examples
The following example removes all primary autotunnels and re-creates them:
Router# clear mpls traffic-eng auto-tunnel primaryRelated Commands
show ip rsvp fast-reroute
Displays information about fast reroutable primary tunnels and their corresponding backup tunnels that provide protection.
clear mpls traffic-eng tunnel counters
To clear the counters for all Multiprotocol Label Switching (MPLS) traffic engineering tunnels, use the clear mpls traffic-eng tunnel counters command in privileged EXEC mode.
clear mpls traffic-eng tunnel counters
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command allows you to set the MPLS traffic engineering tunnel counters to zero so that you can see changes to the counters easily.
Examples
In the following example, the counters for all MPLS traffic engineering tunnels are cleared and a request is made for confirmation that the specified action occurred:
Router# clear mpls traffic-eng tunnel countersClear traffic engineering tunnel counters [confirm]Related Commands
show mpls traffic-eng tunnels statistics
Displays event counters for one or more MPLS traffic engineering tunnels.
clear pw-udp vc
To clear pseudowire User Datagram Protocol (UDP) virtual circuit (VC) counter values, use the clear pw-udp vc command in privileged EXEC mode.
clear pw-udp vc {min-vc max-vc | destination address vcid min-vc max-vc | vcid min-vc max-vc} counters
Syntax Description
Command Default
The pseudowire UDP VC counter values are not cleared.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example shows how to clear the pseudowire UDP VC counter values:
Router# clear pw-udp vc destination 10.1.1.1 countersRelated Commands
clear xconnect
To remove xconnect attachment circuits and pseudowires, use the clear xconnect command in privileged EXEC configuration mode.
clear xconnect {all | interface interface | peer ip-address {all | vcid vc-id}}
Syntax Description
Command Default
xconnect attachment circuits and pseudowires are not removed.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example removes all xconnects:
Router# clear xconnect all02:13:56: Xconnect[ac:Et1/0.1(Eth VLAN)]: provisioning fwder with fwd_type=1, sss_role=102:13:56: Xconnect[mpls:10.1.1.2:1234000]: provisioning fwder with fwd_type=2, sss_role=202:13:56: Xconnect[ac:Et1/0.2(Eth VLAN)]: provisioning fwder with fwd_type=1, sss_role=202:13:56: Xconnect[mpls:10.1.1.2:1234001]: provisioning fwder with fwd_type=2, sss_role=102:13:56: Xconnect[ac:Et1/0.3(Eth VLAN)]: provisioning fwder with fwd_type=1, sss_role=102:13:56: Xconnect[mpls:10.1.2.2:1234002]: provisioning fwder with fwd_type=2, sss_role=202:13:56: Xconnect[ac:Et1/0.4(Eth VLAN)]: provisioning fwder with fwd_type=1, sss_role=202:13:56: Xconnect[mpls:10.1.2.2:1234003]: provisioning fwder with fwd_type=2, sss_role=102:13:56: MPLS peer 10.1.1.2 vcid 1234000, VC DOWN, VC state DOWN02:13:56: MPLS peer 10.1.1.2 vcid 1234001, VC DOWN, VC state DOWN02:13:56: MPLS peer 10.1.2.2 vcid 1234002, VC DOWN, VC state DOWN02:13:56: MPLS peer 10.1.2.2 vcid 1234003, VC DOWN, VC state DOWN02:13:56: XC AUTH [Et1/0.1, 1001]: Event: start xconnect authorization, state changed from IDLE to AUTHORIZING02:13:56: XC AUTH [Et1/0.1, 1001]: Event: found xconnect authorization, state changed from AUTHORIZING to DONE02:13:56: XC AUTH [Et1/0.3, 1003]: Event: start xconnect authorization, state changed from IDLE to AUTHORIZING02:13:56: XC AUTH [Et1/0.3, 1003]: Event: found xconnect authorization, state changed from AUTHORIZING to DONE02:13:56: XC AUTH [10.1.1.2, 1234001]: Event: start xconnect authorization, state changed from IDLE to AUTHORIZING02:13:56: XC AUTH [10.1.1.2, 1234001]: Event: found xconnect authorization, state changed from AUTHORIZING to DONE02:13:56: XC AUTH [10.1.2.2, 1234003]: Event: start xconnect authorization, state changed from IDLE to AUTHORIZING02:13:56: XC AUTH [10.1.2.2, 1234003]: Event: found xconnect authorization, state changed from AUTHORIZING to DONE02:13:56: XC AUTH [Et1/0.1, 1001]: Event: free xconnect authorization request, state changed from DONE to END02:13:56: XC AUTH [Et1/0.3, 1003]: Event: free xconnect authorization request, state changed from DONE to END02:13:56: XC AUTH [10.1.1.2, 1234001]: Event: free xconnect authorization request, state changed from DONE to END02:13:56: XC AUTH [10.1.2.2, 1234003]: Event: free xconnect authorization request, state changed from DONE to END02:13:56: MPLS peer 10.1.1.2 vcid 1234001, VC UP, VC state UP02:13:56: MPLS peer 10.1.2.2 vcid 1234003, VC UP, VC state UP02:13:56: MPLS peer 10.1.1.2 vcid 1234000, VC UP, VC state UP02:13:56: MPLS peer 10.1.2.2 vcid 1234002, VC UP, VC state UPThe following example removes all the xconnects associated with peer router 10.1.1.2:
Router# clear xconnect peer 10.1.1.2 all02:14:08: Xconnect[ac:Et1/0.1(Eth VLAN)]: provisioning fwder with fwd_type=1, sss_role=102:14:08: Xconnect[mpls:10.1.1.2:1234000]: provisioning fwder with fwd_type=2, sss_role=202:14:08: Xconnect[ac:Et1/0.2(Eth VLAN)]: provisioning fwder with fwd_type=1, sss_role=202:14:08: Xconnect[mpls:10.1.1.2:1234001]: provisioning fwder with fwd_type=2, sss_role=102:14:08: MPLS peer 10.1.1.2 vcid 1234000, VC DOWN, VC state DOWN02:14:08: MPLS peer 10.1.1.2 vcid 1234001, VC DOWN, VC state DOWN02:14:08: XC AUTH [Et1/0.1, 1001]: Event: start xconnect authorization, state changed from IDLE to AUTHORIZING02:14:08: XC AUTH [Et1/0.1, 1001]: Event: found xconnect authorization, state changed from AUTHORIZING to DONE02:14:08: XC AUTH [10.1.1.2, 1234001]: Event: start xconnect authorization, state changed from IDLE to AUTHORIZING02:14:08: XC AUTH [10.1.1.2, 1234001]: Event: found xconnect authorization, state changed from AUTHORIZING to DONE02:14:08: XC AUTH [Et1/0.1, 1001]: Event: free xconnect authorization request, state changed from DONE to END02:14:08: XC AUTH [10.1.1.2, 1234001]: Event: free xconnect authorization request, state changed from DONE to END02:14:08: MPLS peer 10.1.1.2 vcid 1234001, VC UP, VC state UP02:14:08: MPLS peer 10.1.1.2 vcid 1234000, VC UP, VC state UPThe following example removes the xconnects associated with peer router 10.1.1.2 and VC ID 1234001:
Router# clear xconnect peer 10.1.1.2 vcid 123400102:14:23: Xconnect[ac:Et1/0.2(Eth VLAN)]: provisioning fwder with fwd_type=1, sss_role=102:14:23: Xconnect[mpls:10.1.1.2:1234001]: provisioning fwder with fwd_type=2, sss_role=202:14:23: MPLS peer 10.1.1.2 vcid 1234001, VC DOWN, VC state DOWN02:14:23: XC AUTH [Et1/0.2, 1002]: Event: start xconnect authorization, state changed from IDLE to AUTHORIZING02:14:23: XC AUTH [Et1/0.2, 1002]: Event: found xconnect authorization, state changed from AUTHORIZING to DONE02:14:23: XC AUTH [Et1/0.2, 1002]: Event: free xconnect authorization request, state changed from DONE to END02:14:23: MPLS peer 10.1.1.2 vcid 1234001, VC UP, VC state UPThe following example removes the xconnects associated with interface Ethernet 1/0.1:
Router# clear xconnect interface eth1/0.102:14:48: Xconnect[ac:Et1/0.1(Eth VLAN)]: provisioning fwder with fwd_type=1, sss_role=202:14:48: Xconnect[mpls:10.1.1.2:1234000]: provisioning fwder with fwd_type=2, sss_role=102:14:48: MPLS peer 10.1.1.2 vcid 1234000, VC DOWN, VC state DOWN02:14:48: XC AUTH [10.1.1.2, 1234000]: Event: start xconnect authorization, state changed from IDLE to AUTHORIZING02:14:48: XC AUTH [10.1.1.2, 1234000]: Event: found xconnect authorization, state changed from AUTHORIZING to DONE02:14:48: XC AUTH [10.1.1.2, 1234000]: Event: free xconnect authorization request, state changed from DONE to END02:14:48: MPLS peer 10.1.1.2 vcid 1234000, VC UP, VC state UPRelated Commands
show xconnect
Displays information about xconnect attachment circuits and pseudowires,
connect (Frame Relay)
To define connections between Frame Relay permanent virtual circuits (PVCs), use the connect command in global configuration mode. To remove connections, use the no form of this command.
connect connection-name interface dlci {interface dlci | l2transport}
no connect connection-name interface dlci {interface dlci | l2transport}
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
When Frame Relay switching is enabled, the connect command creates switched PVCs in Frame Relay networks.
Examples
The following example shows how to define a connection called "frompls1" with DLCI 100 on serial interface 5/0.
connect frompls1 Serial5/0 100 l2transportThe following example shows how to enable Frame Relay switching and define a connection called "one" between DLCI 16 on serial interface 0 and DLCI 100 on serial interface 1.
frame-relay switchingconnect one serial0 16 serial1 100Related Commands
frame-relay switching
Enables PVC switching on a Frame Relay DCE or NNI.
mpls l2transport route
Enables routing of Frame Relay packets over a specified VC.
connect (L2VPN local switching)
To create Layer 2 data connections between two ports on the same router, use the connect command in global configuration mode. To remove such connections, use the no form of this command.
Syntax for 12.0S, 12.2S and 12.4T Releases
connect connection-name type number [dlci | pvc | pvp] type number [dlci | pvc | pvp] [interworking ip | ethernet]
no connect connection-name type number [dlci | pvc | pvp] type number [dlci | pvc | pvp] [interworking ip | ethernet]
Syntax for Cisco IOS XE Release 2.5 and Later Releases
connect connection-name type number type number
no connect connection-name type number type number
Syntax Description
Command Default
This command is disabled by default.
Command Modes
Global configuration
Command History
Examples
The following example shows an Ethernet interface configured for Ethernet, plus an ATM interface configured for AAL5 Subnetwork Access Protocol (SNAP) encapsulation. The connect command allows local switching between these two interfaces and specifies the interworking type as IP mode.
Router(config)# interface atm 0/0/0Router(config-if)# pvc 0/100 l2transportRouter(cfg-if-atm-l2trans-pvc)# encapsulation aal5snapRouter(config)# interface fastethernet 6/0/0.1Router(config-subif)# encapsulation dot1q 100Router(config)# connect atm-eth-con atm 0/0/0 0/100 fastethernet 6/0/0.1 interworking ipRelated Commands
context
To associate a Simple Network Management Protocol (SNMP) context with a particular virtual private network (VPN) routing and forwarding (VRF) instance, use the context command in VRF configuration mode. To disassociate an SNMP context from a VPN, use the no form of this command.
context context-name
no context context-name
Syntax Description
Command Default
No SNMP contexts are associated with VPNs.
Command Modes
VRF configuration
Command History
Usage Guidelines
Before you use this command to associate an SNMP context with a VPN, you must do the following:
•
•
•
SNMP contexts provide VPN users with a secure way of accessing MIB data. When a VPN is associated with a context, MIB data for that VPN exists in that context. Associating a VPN with a context helps enable service providers to manage networks with multiple VPNs. Creating and associating a context with a VPN enables a provider to prevent the users of one VPN from accessing information about users of other VPNs on the same networking device.
A route distinguisher (RD) is required when you configure an SNMP context. An RD creates routing and forwarding tables and specifies the default route distinguisher for a VPN. The RD is added to the beginning of a IPv4 prefix to make it globally unique. An RD is either ASN relative, which means it is composed of an autonomous system number and an arbitrary number, or it is IP address relative and composed of an IP address and an arbitrary number.
Examples
The following example shows how to create an SNMP context named context1 and associate the context with the VRF named vrf1:
Router(config)# snmp-server context1Router(config)# ip vrf vrf1Router(config-vrf)# rd 100:120Router(config-vrf)# context context1Related Commands
control-word
To enable the Multiprotocol Label Switching (MPLS) control word in an Any Transport over MPLS (AToM) dynamic pseudowire connection, use the control-word command in pseudowire class configuration mode. To set the control word to autosense mode, use the default control-word command. To disable the control word, use the no form of this command.
control-word
default control-word
no control-word
Syntax Description
This command has no arguments or keywords.
Command Default
The control word is set to autosense mode.
Command Modes
Pseudowire class configuration (config-pw-class)
Command History
Usage Guidelines
If the MPLS control word is enabled for a static pseudowire and you disable it at the xconnect level, any option set by the pseudowire class is disabled.
Examples
The following example shows how to enable the control word in an AToM dynamic pseudowire connection:
Router# configure terminalRouter(config)# pseudowire-class cw_enableRouter(config-pw-class)# encapsulation mplsRouter(config-pw-class)# control-wordRouter(config-pw-class)# exitThe following example shows how to enable the control word in an AToM dynamic pseudowire connection and set it to autosense mode:
Router# configure terminalRouter(config)# pseudowire-class cw_enableRouter(config-pw-class)# encapsulation mplsRouter(config-pw-class)# default control-wordRouter(config-pw-class)# exitRelated Commands
description (l2 vfi)
To provide a description of the switching provider edge (PE) router for an L2VPN multisegment pseudowire, use the description command in L2 VFI configuration mode. To remove the description, use the no form of this command.
description string
no description string
Syntax Description
Command Default
The switching PE router does not have a description.
Command Modes
L2 VFI (config-vfi)
Command History
Usage Guidelines
This description is useful for tracking the status of each switching PE router.
Examples
This example adds a description for switching PE router 2:
Router(config)# l2 vfi domain_a point-to-pointRouter(config-vfi)# description s-pe2Related Commands
show mpls l2 transport vc detail
Displays the status information about the pseudowire, including the switching PE router.
