-
Cisco IOS Multiprotocol Label Switching Command Reference
-
MPLS Commands: A through L
-
MPLS Commands: match mpls label through mpls label range
-
MPLS Commands: mpls ldp address-message through mpls ldp tcp pak-priority
-
MPLS Commands: mpls mtu through mpls traffic-eng tunnels
-
MPLS Commands: neighbor activate through show controllers xtagatm
-
MPLS Commands: show interface xtagatm through show isis mpls traffic-eng tunnel
-
MPLS Commands: show xtagatm cos-bandwidth-allocation through xconnect
-
MPLS Commands: show mpls atm-ldp bindings through show mpls traffic-eng summary
-
Introduction
-
Table Of Contents
set mpls experimental imposition
show controllers vsi control-interface
show controllers vsi descriptor
neighbor activate
To enable the exchange of information with a Border Gateway Protocol (BGP) neighbor, use the neighbor activate command in address family configuration mode or router configuration mode. To disable the exchange of an address with a BGP neighbor, use the no form of this command.
neighbor {ip-address | peer-group-name | ipv6-address} activate
no neighbor {ip-address | peer-group-name | ipv6-address} activate
Syntax Description
Defaults
The exchange of addresses with BGP neighbors is enabled for the IPv4 address family. Enabling address exchange for all other address families is disabled.
Note
Address exchange for address family IPv4 is enabled by default for each BGP routing session configured with the neighbor remote-as command unless you configure the no bgp default ipv4-activate command before configuring the neighbor remote-as command, or you disable address exchange for address family IPv4 with a specific neighbor by using the no form of the neighbor activate command.
Command Modes
Address family configuration
Router configurationCommand History
Usage Guidelines
Use this command to advertise address information in the form of an IP or IPv6 prefix. The address prefix information is known as Network Layer Reachability Information (NLRI) in BGP.
Examples
Address Exchange Example for Address Family vpn4
The following example shows how to enable address exchange for address family vpnv4 for all neighbors in the BGP peer group named PEPEER and for the neighbor 144.0.0.44:
Router(config)# address-family vpnv4Router(config-router-af)# neighbor PEPEER activateRouter(config-router-af)# neighbor 144.0.0.44 activateRouter(config-router-af)# exit-address-familyAddress Exchange Example for Address Family IPv4 unicast
The following example shows how to enable address exchange for address family IPv4 unicast for all neighbors in the BGP peer group named group1 and for the BGP neighbor 172.16.1.1:
Router(config)# address-family ipv4 unicastRouter(config-router-af)# neighbor group1 activateRouter(config-router-af)# neighbor 172.16.1.1 activateAddress Exchange Example for Address Family IPv6
The following example shows how to enable address exchange for address family IPv6 for all neighbors in the BGP peer group named group2 and for the BGP neighbor 7000::2:
Router(config)# address-family ipv6Router(config-router-af)# neighbor group2 activateRouter(config-router-af)# neighbor 7000::2 activateRelated Commands
neighbor allowas-in
To configure provider edge (PE) routers to allow readvertisement of all prefixes containing duplicate autonomous system numbers (ASNs), use the neighbor allowas-in command in router configuration mode. To disable the readvertisement of the ASN of the PE router, use the no form of this command.
neighbor ip-address allowas-in [number]
no neighborip-address allowas-in [number]
Syntax Description
Defaults
Readvertisement of all prefixes containing duplicate ASNs is disabled by default.
Command Modes
Router configuration
Command History
Usage Guidelines
In a hub and spoke configuration, a PE router readvertises all prefixes containing duplicate autonomous system numbers. Use the neighbor allowas-in command to configure two VRFs on each PE router to receive and readvertise prefixes are as follows:
•
•
You control the number of times an ASN is advertised by specifying a number from 1 to 10.
Examples
The following example shows how to configure the PE router with ASN 100 to allow prefixes from the VRF address family Virtual Private Network (VPN) IPv4 vrf1. The neighboring PE router with the IP address 192.168.255.255 is set to be readvertised to other PE routers with the same ASN six times.
Router(config)# router bgp 100Router(config-router)# address-family ipv4 vrf vrf1Router(config-router)# neighbor 192.168.255.255 allowas-in 6Related Commands
address-family
Enters the address family configuration submode used to configure routing protocols such as BGP, OSPF, RIP, and static routing.
neighbor as-override
To configure a provider edge (PE) router to override the autonomous system number (ASN) of a site with the ASN of a provider, use the neighbor as-override command in router configuration mode. To remove Virtual Private Network (VPN) IPv4 prefixes from a specified router, use the no form of this command.
neighbor ip-address as-override
no neighbor ip-address as-override
Syntax Description
Defaults
Automatic override of the ASN is disabled.
Command Modes
Router configuration
Command History
Usage Guidelines
This command is used in conjunction with the site-of-origin feature, identifying the site where a route originated, and preventing routing loops between routers within a VPN.
Examples
The following example shows how to configure a router to override the ASN of a site with the ASN of a provider:Router(config)# router bgp 100Router(config-router)# neighbor 192.168.255.255 remote-as 109Router(config-router)# neighbor 192.168.255.255 update-source loopback0Router(config-router)# address-family ipv4 vrf vpn1Router(config-router)# neighbor 192.168.255.255 activateRouter(config-router)# neighbor 192.168.255.255 as-overrideRelated Commands
neighbor send-label
To enable a Border Gateway Protocol (BGP) router to send Multiprotocol Label Switching (MPLS) labels with BGP routes to a neighboring BGP router, use the neighbor send-label command in address family configuration mode or router configuration mode. To disable this feature, use the no form of this command.
neighbor ip-address send-label
no neighbor ip-address send-label
Syntax Description
Defaults
BGP routers distribute only BGP routes.
Command Modes
Address family configuration
Router configurationCommand History
Usage Guidelines
This command enables a router to use BGP to distribute MPLS labels along with the IPv4 routes to a peer router. You must issue this command on both the local router and the neighboring router.
This command has the following restrictions:
•
•
Use this command in IPv6 address family configuration mode to bind and advertise IPv6 prefix MPLS labels. Using this command in conjunction with the mpls ipv6 source-interface global configuration command allows IPv6 traffic to run over an IPv4 MPLS network without any software or hardware configuration changes in the backbone. Edge routers configured to run both IPv4 and IPv6 forward IPv6 traffic using MPLS and multiprotocol internal BGP (MP-iBGP).
Examples
The following example shows how to enable a router in the autonomous system 65000 to send MPLS labels with BGP routes to the neighbor BGP router at 192.168.0.1:
Router(config)# router bgp 65000Router(config-router)# neighbor 192.168.0.1 remote-as 65001Router(config-router)# neighbor 192.168.0.1 send-labelThe following example shows how to enable a router in the autonomous system 65000 to bind and advertise IPv6 prefix MPLS labels and send the labels with BGP routes to the neighbor BGP router at 192.168.99.70:
Router(config)# router bgp 65000Router(config-router)# neighbor 192.168.99.70 remote-as 65000Router(config-router)# address-family ipv6Router(config-router-af)# neighbor 192.168.99.70 activateRouter(config-router-af)# neighbor 192.168.99.70 send-labelRelated Commands
next-address
To specify the next IP address in the explicit path, use the next-address command in IP explicit path configuration mode. To remove the specified next IP address in the explicit path, use the no form of this command.
next-address A.B.C.D
no next-address A.B.C.D
Syntax Description
Defaults
Next IP address in the explicit path is not specified.
Command Modes
IP explicit path configuration
Command History
Examples
The following example shows how to assign the number 60 to the IP explicit path, enable the path, and specify 10.3.27.3 as the next IP address in the list of IP addresses:
Router(config)# ip explicit-path identifier 60 enableRouter(cfg-ip-expl-path)# next-address 10.3.27.3Explicit Path identifier 60:1: next-address 10.3.27.3Router(cfg-ip-exp1-path)#Related Commands
oam retry
To configure parameters related to Operation, Administration, and Maintenance (OAM) management for an ATM permanent virtual circuit (PVC), switched virtual circuit (SVC), VC class, or VC bundle, or label-controlled ATM (LC-ATM) VC, use the oam retry command in the appropriate command mode. To remove OAM management parameters, use the no form of this command.
oam retry up-count down-count retry-frequency
no oam retry
Syntax Description
Defaults
ATM PVCs and SVCs
up-count: 3
down-count: 5
retry-frequency: 1 secondLC-ATM VCs
up-count: 2
down-count: 2
retry-frequency: 2 secondsCommand Modes
Interface-ATM-VC configuration (for an ATM PVC or SVC)
VC-class configuration (for a VC class)
Bundle configuration mode (for a VC bundle)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)
Control-VC configuration (for an LC-ATM VC)Command History
Usage Guidelines
The following guidelines apply to PVCs, SVCs, and VC classes. They do not apply to LC-ATM VCs.
•
–
–
–
–
•
•
–
–
–
Examples
The following example shows how to configure the OAM management parameters with an up count of 3, a down-count of 3, and the retry frequency set at 10 seconds:
Router(cfg-mpls-atm-cvc)# oam retry 3 3 10Related Commands
oam-ac emulation-enable
To enable Operation, Administration, and Maintenance (OAM) cell emulation on ATM adaptation layer 5 (AAL5) over Multiprotocol Label Switching (MPLS), use the oam-ac emulation-enable command in the appropriate configuration mode on both provider edge (PE) routers. To disable OAM cell emulation, use the no form of this command on both routers.
oam-ac emulation-enable [ais-rate]
no oam-ac emulation-enable [ais-rate]
Syntax Description
Defaults
OAM cell emulation is disabled. If you enable OAM cell emulation without specifying an AIS rate, the default is to send one AIS cell every second.
Command Modes
L2transport VC configuration mode for an ATM PVC
VC class configuration mode for a VC class
Command History
Usage Guidelines
This command is only applicable to AAL5 over MPLS and is not supported with ATM Cell Relay over MPLS.
Examples
The following example shows how to enable OAM cell emulation on an ATM PVC:
Router# interface ATM 1/0/0Router(config-if)# pvc 1/200 l2transport
Router(config-if-atm-l2trans-pvc)# oam-ac emulation-enableThe following example shows how to set the rate at which an AIS cell is sent to every 30 seconds:
Router# interface ATM 1/0/0Router(config-if)# pvc 1/200 l2transport
Router(config-if-atm-l2trans-pvc)# oam-ac emulation-enable 30The following example configures OAM cell emulation for ATM AAL5 over MPLS in VC class configuration mode. The VC class is then applied to an interface.
Router> enableRouter# configure terminalRouter(config)# vc-class atm oamclassRouter(config-vc-class)# encapsulation aal5Router(config-vc-class)# oam-ac emulation-enable 30
Router(config-vc-class)# oam-pvc manage
Router(config)# interface atm1/0Router(config-if)# class-int oamclassRouter(config-if)# pvc 1/200 l2transportRouter(config-if-atm-l2trans-pvc)# xconnect 13.13.13.13 100 encapsulation mplsRelated Commands
oam-pvc
To enable end-to-end F5 Operation, Administration, and Maintenance (OAM) loopback cell generation and OAM management for an ATM permanent virtual circuit (PVC), virtual circuit (VC) class, or label-controlled ATM (LC-ATM) VC, use the oam-pvc command in the appropriate command mode. To disable generation of OAM loopback cells and OAM management, use the no form of this command.
ATM VC or VC Class
oam-pvc [manage] [frequency]
no oam-pvc [manage]
LC-ATM VC
oam-pvc manage [frequency]
no oam-pvc manage
Loopback Mode Detection
oam-pvc manage [frequency] loop-detection
no oam-pvc manage loop-detection
Syntax Description
Command Default
Disabled.
Command Modes
Interface-ATM-VC configuration (for an ATM PVC or Loopback Mode Detection)
VC-class configuration (for a VC class)
PVC-in-range configuration (for an individual PVC within a PVC range)
Control-VC configuration (for enabling OAM management on an LC-ATM VC)Command History
Usage Guidelines
If OAM management is enabled, further control of OAM management is configured using the oam retry command.
ATM VCS or VC Classes
If the oam-pvc command is not explicitly configured on an ATM PVC, the PVC inherits the following default configuration (listed in order of precedence):
•
•
•
•
Loopback Mode Detection
When a PVC traverses an ATM cloud and OAM is enabled, the router sends a loopback cell to the other end and waits for a response to determine whether the circuit is up. If an intervening router within the ATM cloud is in loopback mode, however, the router considers the circuit to be up, when in fact the other end is not reachable.
When enabled, the Loopback Mode Detection Through OAM feature detects when an intervening router is in loopback mode, in which case it sets the OAM state to NOT_VERIFIED. This prevents traffic from being routed on the PVC for as long as any intervening router is detected as being in loopback mode.
Examples
The following example shows how to enable end-to-end F5 OAM loopback cell transmission and OAM management on an ATM PVC with a transmission frequency of 3 seconds:
Router(cfg-mpls-atm-cvc)# oam-pvc manage 3The following example shows how to enable end-to-end F5 OAM loopback cell transmission and OAM management on an LC-ATM interface with a transmission frequency of 2 seconds:
Router(config)# interface Switch1.10 mplsRouter(config-subif)# ip unnumbered Loopback0Router(config-subif)# mpls atm control-vc 0 32Router(cfg-mpls-atm-cvc)# oam-pvc manage 2The following example shows how to create a PVC and enable loopback detection:
Router(config)# interface ATM1/0Router(config-if)# pvc 4/100Router(config-if-atm-vc)# oam-pvc manage loop-detectionRelated Commands
pseudowire
To bind an attachment circuit to a Layer 2 pseudowire for xconnect service, use the pseudowire command in interface configuration mode.
pseudowire peer-ip-address vcid pw-class pw-class-name [sequencing {transmit | receive | both}]
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
The combination of the peer-ip-address and vcid arguments must be unique on the router. Each pseudowire configuration must have a unique combination of peer-ip-address and vcid configuration.
The same vcid value that identifies the attachment circuit must be configured using the pseudowire command on the local and remote router at each end of a Layer 2 session. The virtual circuit identifier creates the binding between a pseudowire and an attachment circuit.
The pw-class pw-class-name value binds the pseudowire configuration of an attachment circuit to a specific pseudowire class. In this way, the pseudowire class configuration serves as a template that contains settings used by all attachment circuits bound to it with the pseudowire command.
Examples
The following example creates a virtual-PPP interface with the number 1, configures PPP on the virtual-PPP interface, and binds the attachment circuit to a Layer 2 pseudowire for xconnect service for the pseudowire class named pwclass1:
interface virtual-ppp 1ppp authentication chapppp chap hostname peer1pseudowire 172.24.13.196 10 pw-class pwclass1Related Commands
pseudowire-class
To specify the name of a Layer 2 pseudowire class and enter pseudowire class configuration mode, use the pseudowire-class command in global configuration mode.
pseudowire-class [pw-class-name]
Syntax Description
pw-class-name
(Optional) The name of a Layer 2 pseudowire class. If you want to configure more than one pseudowire class, you must enter a value for the pw-class-name argument.
Defaults
No pseudowire class is defined.
Command Modes
Global configuration
Command History
12.0(23)S
This command was introduced.
12.3(2)T
This command was integrated into Cisco IOS Release 12.3(2)T.
Usage Guidelines
The pseudowire-class command allows you to configure a pseudowire class template that consists of configuration settings used by all attachment circuits bound to the class. A pseudowire class includes the following configuration settings:
•
•
•
•
•
After you enter the pseudowire-class command, the router switches to pseudowire class configuration mode, where pseudowire settings may be configured.
Examples
The following example shows how to enter pseudowire class configuration mode to configure a pseudowire configuration template named "ether-pw":
Router(config)# pseudowire-class ether-pwRouter(config-pw)#Related Commands
rd
To create routing and forwarding tables for a Virtual Private Network (VPN) routing/forwarding instance (VRF), use the rd command in VRF configuration mode.
rd route-distinguisher
Syntax Description
Defaults
There is no default. A route distinguisher (RD) must be configured for a VRF to be functional.
Command Modes
VRF configuration
Command History
Usage Guidelines
An RD creates routing and forwarding tables and specifies the default route distinguisher for a VPN. The RD is added to the beginning of the customer's IPv4 prefixes to change them into globally unique VPN-IPv4 prefixes.
Either RD is an ASN-relative RD, in which case it is composed of an autonomous system number and an arbitrary number, or it is an IP-address-relative RD, in which case it is composed of an IP address and an arbitrary number.
You can enter an RD in either of these formats:
16-bit AS number: your 32-bit number
For example, 101:3.32-bit IP address: your 16-bit number
For example, 192.168.122.15:1.Examples
The following example shows how to configure a default RD for two VRFs. It illustrates the use of both AS-relative and IP-address-relative RDs:
Router(config)# ip vrf vrf_blueRouter(config-vrf)# rd 100:3Router (config-vrf)# exitRouter(config)# ip vrf vrf_redRouter(config-vrf)# rd 173.13.0.12:200Related Commands
ip vrf
Configures a VRF routing table.
show ip vrf
Displays the set of defined VRFs and associated interfaces.
route-target
To create a route-target extended community for a Virtual Private Network (VPN) routing/forwarding instance (VRF), use the route-target command in VRF configuration mode. To disable the configuration of a route-target community option, use the no form of this command.
route-target {import | export | both} route-target-ext-community
no route-target {import | export | both} route-target-ext-community
Syntax Description
Defaults
There are no defaults. A VRF has no route-target extended community attributes associated with it until specified by the route-target command.
Command Modes
VRF configuration
Command History
Usage Guidelines
The route-target command creates lists of import and export route-target extended communities for the specified VRF. Enter the command one time for each target community. Learned routes that carry a specific route-target extended community are imported into all VRFs configured with that extended community as an import route target. Routes learned from a VRF site (for example, by Border Gateway Protocol (BGP), Routing Information Protocol (RIP), or static route configuration) contain export route targets for extended communities configured for the VRF added as route attributes to control the VRFs into which the route is imported.
The route target specifies a target VPN extended community. Like a route-distinguisher, an extended community is composed of either an autonomous system number and an arbitrary number or an IP address and an arbitrary number. You can enter the numbers in either of these formats:
16-bit AS number:your 32-bit number
For example, 101:3.32-bit IP address:your 16-bit number
For example, 192.168.122.15: 1.Examples
The following example shows how to configure route-target extended community attributes for a VRF. The result of the command sequence is that VRF named vrf_blue has two export extended communities (1000:1 and 1000:2) and two import extended communities (1000:1 and 173.27.0.130:200).
Router(config)# ip vrf vrf_blueRouter(config-vrf)# route-target both 1000:1Router(config-vrf)# route-target export 1000:2Router(config-vrf)# route-target import 173.27.0.130:200Related Commands
import map
Configures an import route map for a VRF.
ip vrf
Configures a VRF routing table.
sequencing
To configure the direction in which sequencing is enabled for data packets in a Layer 2 pseudowire, use the sequencing command in pseudowire class configuration mode. To remove the sequencing configuration from the pseudowire class, use the no form of this command.
sequencing {transmit | receive | both | resync {number}}
no sequencing {transmit | receive | both | resync {number}}
Syntax Description
Defaults
Sequencing is disabled.
Command Modes
Pseudowire class configuration
Command History
Usage Guidelines
•
•
•
•
Examples
The following example shows how to enable sequencing in data packets in Layer 2 pseudowires that were created from the pseudowire class named "ether-pw" so that the Sequence Number field is updated in tunneled packet headers for data packets that are both sent and received over the pseudowire:
Router(config)# pseudowire-class ether-pwRouter(config-pw)# encapsulation mplsRouter(config-pw)# sequencing bothThe following example shows how to enable the disposition router to reset packet sequencing after it receives 1000 out-of-order packets:
Router(config)# pseudowire-class ether-pwRouter(config-pw)# encapsulation mplsRouter(config-pw)# sequencing bothRouter(config-pw)# sequencing resync 1000Related Commands
ip cef
Enables CEF on the Route Processor card.
pseudowire-class
Specifies the name of an L2TP pseudowire class and enters pseudowire class configuration mode.
set mpls experimental imposition
To set the value of the Multiprotocol Label Switching (MPLS) experimental (EXP) field on all imposed label entries, use the set mpls experimental imposition command in QoS policy-map class configuration mode. To disable the setting, use the no form of this command.
set mpls experimental imposition {mpls-exp-value | from-field [table table-map-name]}
no set mpls experimental imposition {mpls-exp-value | from-field [table table-map-name]}
Syntax Description
Defaults
No MPLS EXP value is set.
Command Modes
QoS policy-map class configuration
Command History
Usage Guidelines
The set mpls experimental imposition command is supported only on input interfaces. Use this command during label imposition. This command sets the MPLS EXP field on all imposed label entries.
Using This Command with the Enhanced Packet Marking Feature
If you are using this command as part of the Enhanced Packet Marking feature, you can use this command to specify the "from-field" packet-marking category to be used for mapping and setting the class of service (CoS) value. The "from-field" packet-marking categories are as follows:
•
•
If you specify a "from-field" category but do not specify the table keyword and the applicable table-map-name argument, the default action will be to copy the value associated with the "from-field" category as the MPLS EXP imposition value. For instance, if you configure the set mpls experimental imposition precedence command, the precedence value will be copied and used as the MPLS EXP imposition value.
You can configure the set mpls experimental imposition dscp command, and the DSCP value will be copied and used as the MPLS EXP imposition value.
Note
Examples
The following example shows how to set the MPLS EXP value to 3 on all imposed label entries:
Router(config-pmap)# set mpls experimental imposition 3The following example shows how to create the policy map named policy1 to use the packet-marking values defined in a table map named table-map1. The table map was created earlier with the table-map (value mapping) command. For more information about the table-map (value mapping) command, see the table-map (value mapping) command page.
The following example sets the MPLS EXP imposition value according to the DSCP value defined in table-map1.
Router(config)# policy-map policy1 Router(config-pmap)# class class-default Router(config-pmap-c)# set mpls experimental imposition dscp table table-map1Router(config-pmap-c)# exitRelated Commands
set mpls experimental topmost
To set the Multiprotocol Label Switching (MPLS) experimental (EXP) field value in the topmost label on either an input or an output interface, use the set mpls experimental topmost command in QoS policy-map class configuration mode. To disable the setting, use the no form of this command.
set mpls experimental topmost {mpls-exp-value | qos-group [table table-map-name]}
no set mpls experimental topmost {mpls-exp-value | qos-group [table table-map-name]}
Syntax Description
Defaults
No MPLS EXP value is set.
Command Modes
QoS policy-map class configuration
Command History
Usage Guidelines
This command sets the MPLS EXP value only in the topmost label. This command does not affect an IP packet. The MPLS field in the topmost label header is not changed.
Using This Command with the Enhanced Packet Marking Feature
If you are using this command as part of the Enhanced Packet Marking feature, you can use this command to specify the qos-group packet-marking category to be used for mapping and setting the differentiated services code point (DSCP) value.
If you specify the qos-group category but do not specify the table keyword and the applicable table-map-name argument, the default action will be to copy the value associated with the qos-group category as the MPLS EXP topmost value. For instance, if you configure the set mpls experimental topmost qos-group command, the QoS group value will be copied and used as the MPLS EXP topmost value.
The valid value range for the MPLS EXP topmost value is a number from 0 to 7. The valid value range for the QoS group is a number from 0 to 99. Therefore, when configuring the set mpls experimental topmost qos-group command, note the following points:
•
•
Examples
The following example shows how to set the MPLS EXP value to 3 in the topmost label of an input or output interface:
Router(config-pmap)# set mpls experimental topmost 3The following example shows how to create the policy map named policy1 to use the packet-marking values defined in a table map named table-map1. The table map was created earlier with the table-map (value mapping) command. For more information about the table-map (value mapping) command, see the table-map (value mapping) command page.
The following example shows how to set the MPLS EXP value according to the QoS group value defined in table-map1.
Router(config)# policy-map policy1Router(config-pmap)# class class-defaultRouter(config-pmap-c)# set mpls experimental topmost qos-group table table-map1Router(config-pmap-c)# exitRelated Commands
set mpls-label
To enable a route to be distributed with a Multiprotocol Label Switching (MPLS) label if the route matches the conditions specified in the route map, use the set mpls-label command in route map configuration mode. To disable this function, use the no form of this command.
set mpls-label
no set mpls-label
Syntax Description
This command has no arguments or keywords.
Defaults
No route with an MPLS label is distributed.
Command Modes
Route map configuration
Command History
Usage Guidelines
This command can be used only with the neighbor route-map out command to manage outbound route maps for a Border Gateway Protocol (BGP) session.
Use the route-map global configuration command with 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.
Examples
The following example shows how to create a route map that enables the route to be distributed with a label if the IP address of the route matches an IP address in ACL 1.
Router(config-router)# route-map incoming permit 10Router(config-route-map)# match ip address 1Router(config-route-map)# set mpls-labelRelated Commands
set ospf router-id
To set a separate Open Shortest Path First (OSPF) router ID for each interface or subinterface on a provider edge (PE) router for each directly attached customer edge (CE) router, use the set ospf router-id command in route map configuration mode.
set ospf router-id
Syntax Description
This command has no arguments or keywords.
Defaults
OSPF router ID is not set.
Command Modes
Route map configuration
Command History
Usage Guidelines
To use this command, you must enable OSPF and create a routing process.
Examples
The following example shows how to match the PE router IP address 192.168.0.0 against the interface in access list 1 and set to the OSPF router ID:
router ospf 2 vrfvpn1-site1redistribute bgp 100 metric-type 1 subnetsnetwork 202.0.0.0 0.0.0.255 area 1router bgp 100neighbor 172.19.89. 62 remote-as 100access-list 1 permit 192.168.0.0route-map vpn1-site1-map permit 10match ip address 1set ospf router-idRelated Commands
router ospf
Enables OSPF routing, which places the router in router configuration mode.
set vrf
To enable Virtual Private Network (VPN) routing/forwarding instance (VRF) selection within a route map for policy-based routing VRF selection, use the set vrf command in route-map configuration mode. To disable VRF selection within a route map, use the no form of this command.
set vrf vrf-name
no set vrf vrf-name
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-map configuration
Command History
12.3(7)T
This command was introduced.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
Usage Guidelines
The set vrf route-map configuration command was introduced with the MPLS VPN—VRF Selection using Policy Based Routing feature to provide a PBR mechanism for VRF selection. This command is used to enable VRF selection by policy routing packets through a route map. The route map is attached to the incoming interface. Match criteria is defined in an IP access list or in an IP prefix list. Match criteria can also be defined based on packet length with the match length route map command. The VRF must be defined prior to the configuration of this command, and the ip policy route-map interface configuration command must be configured to enable policy routing under the interface or subinterface. If the VRF is not defined or if policy routing is not enabled, an error message will be printed in the console when you attempt to configure the set vrf command.
Note
Examples
The following example shows a route-map sequence that selects and sets a VRF based on match criteria defined in three different access lists. (The access list configuration is not shown in this example.) If the route map falls through and a match does not occur, the packet will be dropped if the destination is local.
route-map PBR-VRF-Selection permit 10match ip address 40set vrf VRF_1!route-map PBR-VRF-Selection permit 20match ip address 50set vrf VRF_2!route-map PBR-VRF-Selection permit 30match ip address 60set vrf VRF_3Related Commands
show connection
To display the status of interworking connections, use the show connection command in EXEC mode.
show connection [all | element | id ID | name name | port port]
Syntax Description
Defaults
Default state is show connection all.
Command Modes
EXEC
Command History
Examples
The following example shows the local interworking connections on a router:
Router# show connectionID Name Segment 1 Segment 2 State========================================================================1 conn1 ATM 1/0/0 AAL5 0/100 ATM 2/0/0 AAL5 0/100 UP2 conn2 ATM 2/0/0 AAL5 0/300 Serial0/1 16 UP3 conn3 ATM 2/0/0 AAL5 0/400 FA 0/0.1 10 UP4 conn4 ATM 1/0/0 CELL 0/500 ATM 2/0/0 CELL 0/500 UP5 conn5 ATM 1/0/0 CELL 100 ATM 2/0/0 CELL 100 UPTable 1 describes the significant fields shown in the display.
Related Commands
show atm pvc
Displays the status of ATM PVCs and SVCs.
show frame-relay pvc
Displays the status of Frame Relay interfaces.
show controllers vsi control-interface
To display information about an ATM interface configured with the tag-control-protocol vsi command to control an external switch (or if an interface is not specified, to display information about all Virtual Switch Interface [VSI] control interfaces), use the show controllers vsi control-interface command in user EXEC or privileged EXEC mode.
show controllers vsi control-interface [interface]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show controllers vsi control-interface command:
Router# show controllers vsi control-interfaceInterface: ATM2/0 Connections: 14The display shows the number of cross-connects currently on the switch that were established by the MPLS LSC through the VSI over the control interface.
Related Commands
show controllers vsi descriptor
To display information about a switch interface discovered by the Multiprotocol Label Switching (MPLS) Label Switch Controller (LSC) through a Virtual Switch Interface (VSI), or if no descriptor is specified, about all such discovered interfaces, use the show controllers vsi descriptor command in user EXEC or privileged EXEC mode.
show controllers vsi descriptor [descriptor]
Syntax Description
descriptor
(Optional) Physical descriptor. For the Cisco BPX switch, the physical descriptor has the following form: slot.port.0
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Specify an interface by its (switch-supplied) physical descriptor.
Per-interface information includes the following:
•
•
•
•
•
•
•
•
Similar information is displayed when you enter the show controllers xtagatm privileged EXEC command. However, you must specify a Cisco IOS interface name instead of a physical descriptor.
Examples
The following is sample output from the show controllers vsi descriptor command:
Router# show controllers vsi descriptor 12.2.0Phys desc: 12.2.0Log intf: 0x000C0200 (0.12.2.0)Interface: XTagATM0IF status: up IFC state: ACTIVE Min VPI: 1 Maximum cell rate: 10000 Max VPI: 259 Available channels: 2000 Min VCI: 32 Available cell rate (forward): 10000 Max VCI: 65535 Available cell rate (backward): 10000Table 2 describes the significant fields shown in the display.
Related Commands
show controllers xtagatm
Displays information about an extended MPLS ATM interface.
show controllers vsi session
To display information about all sessions with Virtual Switch Interface (VSI) slaves, use the show controllers vsi session command in user EXEC or privileged EXEC mode.
show controllers vsi session [session-number [interface interface]]
Note
Syntax Description
session-number
(Optional) Specifies the session number.
interface interface
(Optional) Specifies the VSI control interface.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
If a session number and an interface are specified, detailed information on the individual session is presented. If the session number is specified, but the interface is omitted, detailed information on all sessions with that number is presented. (Only one session can contain a given number, because multiple control interfaces are not supported.)
Examples
The following is sample output from the show controllers vsi session command:
Router# show controllers vsi sessionInterface Session VCD VPI/VCI Switch/Slave Ids Session StateATM0/0 0 1 0/40 0/1 ESTABLISHED ATM0/0 1 2 0/41 0/2 ESTABLISHED ATM0/0 2 3 0/42 0/3 DISCOVERY ATM0/0 3 4 0/43 0/4 RESYNC-STARTING ATM0/0 4 5 0/44 0/5 RESYNC-STOPPING ATM0/0 5 6 0/45 0/6 RESYNC-UNDERWAY ATM0/0 6 7 0/46 0/7 UNKNOWN ATM0/0 7 8 0/47 0/8 UNKNOWN ATM0/0 8 9 0/48 0/9 CLOSING ATM0/0 9 10 0/49 0/10 ESTABLISHED ATM0/0 10 11 0/50 0/11 ESTABLISHED ATM0/0 11 12 0/51 0/12 ESTABLISHEDTable 3 describes the significant fields shown in the display.
In the following example, session number 9 is specified with the show controllers vsi session command:
Router# show controllers vsi session 9Interface: ATM1/0 Session number: 9VCD: 10 VPI/VCI: 0/49Switch type: BPX Switch id: 0Controller id: 1 Slave id: 10Keepalive timer: 15 Powerup session id: 0x0000000ACfg/act retry timer: 8/8 Active session id: 0x0000000AMax retries: 10 Ctrl port log intf: 0x000A0100Trap window: 50 Max/actual cmd wndw: 21/21Trap filter: all Max checksums: 19Current VSI version: 1 Min/max VSI version: 1/1Messages sent: 2502 Inter-slave timer: 4.000Messages received: 2502 Messages outstanding: 0Table 4 describes the significant fields shown in the display.
Related Commands
show controllers vsi status
To display a one-line summary of each Virtual Switch Interface (VSI)-controlled interface, use the show controllers vsi status command in user EXEC or privileged EXEC mode.
show controllers vsi status
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
If an interface is discovered by the LSC, but no extended Multiprotocol Label Switching (MPLS) ATM interface is associated with it through the extended-port command, then the interface name is marked <unknown>, and interface status is marked n/a.
Examples
The following is sample output from the show controllers vsi status command:
Router# show controllers vsi statusInterface Name IF Status IFC State Physical Descriptor switch control port n/a ACTIVE 12.1.0 XTagATM0 up ACTIVE 12.2.0 XTagATM1 up ACTIVE 12.3.0 <unknown> n/a FAILED-EXT 12.4.0Table 5 describes the significant fields shown in the display.
show controllers vsi traffic
To display traffic information about Virtual Switch Interface (VSI)-controlled interfaces, VSI sessions, or virtual circuits (VCs) on VSI-controlled interfaces, use the show controllers vsi traffic command in user EXEC or privileged EXEC mode.
show controllers vsi traffic {descriptor descriptor | session session-number | vc [descriptor descriptor [vpi vci]]}
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
12.0(5)T
This command was introduced.
12.2(4)T
The VPI range of values was extended to 4095.
Usage Guidelines
If none of the keywords is specified, traffic for all interfaces is displayed. You can specify a single interface by its (switch-supplied) physical descriptor. For the BPX switch, the physical descriptor has the form
slot.port. 0
If a session number is specified, the output displays VSI protocol traffic by message type. The VC traffic display is also displayed by the show xmplsatm vc cross-connect traffic descriptor command.
Examples
The following is sample output from the show controllers vsi traffic command:
Router# show controllers vsi trafficPhys desc: 10.1.0Interface: switch control portIF status: n/aRx cells: 304250 Rx cells discarded: 0Tx cells: 361186 Tx cells discarded: 0Rx header errors: 4294967254 Rx invalid addresses (per card): 80360Last invalid address: 0/53Phys desc: 10.2.0Interface: XTagATM0IF status: upRx cells: 202637 Rx cells discarded: 0Tx cells: 194979 Tx cells discarded: 0Rx header errors: 4294967258 Rx invalid addresses (per card): 80385Last invalid address: 0/32Phys desc: 10.3.0Interface: XTagATM1IF status: upRx cells: 182295 Rx cells discarded: 0Tx cells: 136369 Tx cells discarded: 0Rx header errors: 4294967262 Rx invalid addresses (per card): 80372Last invalid address: 0/32Table 6 describes the significant fields shown in the display.
The following sample output is displayed when you enter the show controllers vsi traffic session 9 command:
Router# show controllers vsi traffic session 9Sent ReceivedSw Get Cnfg Cmd: 3656 Sw Get Cnfg Rsp: 3656Sw Cnfg Trap Rsp: 0 Sw Cnfg Trap: 0Sw Set Cnfg Cmd: 1 Sw Set Cnfg Rsp: 1Sw Start Resync Cmd: 1 Sw Start Resync Rsp: 1Sw End Resync Cmd: 1 Sw End Resync Rsp: 1Ifc Getmore Cnfg Cmd: 1 Ifc Getmore Cnfg Rsp: 1Ifc Cnfg Trap Rsp: 4 Ifc Cnfg Trap: 4Ifc Get Stats Cmd: 8 Ifc Get Stats Rsp: 8Conn Cmt Cmd: 73 Conn Cmt Rsp: 73Conn Del Cmd: 50 Conn Del Rsp: 0Conn Get Stats Cmd: 0 Conn Get Stats Rsp: 0Conn Cnfg Trap Rsp: 0 Conn Cnfg Trap: 0Conn Bulk Clr Stats Cmd: 0 Conn Bulk Clr Stats Rsp: 0Gen Err Rsp: 0 Gen Err Rsp: 0unused: 0 unused: 0unknown: 0 unknown: 0TOTAL: 3795 TOTAL: 3795Table 7 describes the significant fields shown in the display.
show controllers xtagatm
To display information about an extended Multiprotocol Label Switching (MPLS) ATM interface controlled through the Virtual Switch Interface (VSI) protocol (or, if an interface is not specified, to display information about all extended MPLS ATM interfaces controlled through the VSI protocol), use the show controllers xtagatm command in user EXEC or privileged EXEC mode.
show controllers xtagatm if-number
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Per-interface information includes the following:
•
•
•
•
•
•
•
•
Similar information appears if you enter the show controllers vsi descriptor command. However, you must specify an interface by its (switch-supplied) physical descriptor, instead of its Cisco IOS interface name. For the Cisco BPX switch, the physical descriptor has the form slot.port.0.
Examples
In this example, the sample output is from the show controllers xtagatm command specifying interface 0:
Router# show controllers xtagatm 0Interface XTagATM0 is up Hardware is Tag-Controlled ATM Port (on BPX switch BPX-VSI1) Control interface ATM1/0 is up Physical descriptor is 10.2.0 Logical interface 0x000A0200 (0.10.2.0) Oper state ACTIVE, admin state UP VPI range 1-255, VCI range 32-65535 VPI is not translated at end of link Tag control VC need not be strictly in VPI/VCI range Available channels: ingress 30, egress 30 Maximum cell rate: ingress 300000, egress 300000 Available cell rate: ingress 300000, egress 300000 Endpoints in use: ingress 7, egress 8, ingress/egress 1 Rx cells 134747 rx cells discarded 0, rx header errors 0 rx invalid addresses (per card): 52994 last invalid address 0/32 Tx cells 132564 tx cells discarded: 0Table 8 describes the significant fields shown in the display.
Related Commands
show controllers vsi descriptor
Displays information about a switch interface discovered by the MPLS LSC through the VSI.
