match mpls-label through mpls ldp atm control-mode
Available Languages
Table Of Contents
mls mpls (guaranteed bandwidth traffic engineering)
mls mpls qos input uniform-mode
mpls ip (global configuration)
mpls ip (interface configuration)
mpls ip encapsulate explicit-null
mpls label protocol (global configuration)
mpls label protocol (interface configuration)
mpls ldp advertise-labels old-style
match mpls-label
To redistribute routes that include Multiprotocol Label Switching (MPLS) labels if the routes meet the conditions specified in the route map, use the match mpls-label command in route-map configuration mode. To disable this function, use the no form of this command.
match mpls-label
no match mpls-label
Syntax Description
This command has no arguments or keywords.
Command Default
Routes with MPLS labels are not redistributed.
Command Modes
Route-map configuration
Command History
Usage Guidelines
A route map that includes this command can be used in the following instances:
•
With the neighbor route-map in command to manage inbound route maps in BGP
•
Use the route-map global configuration command, and the match and set route map configuration commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria—the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions—the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The match route-map configuration command has multiple formats. The match commands can be given in any order, and all match commands must "pass" to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
When you are passing routes through a route map, a route map can have several parts. Any route that does not match at least one match clause relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want to modify only some data, you must configure a second route map section with an explicit match specified.
Examples
The following example shows how to create a route map that redistributes routes if the following conditions are met:
•
•
Router(config-router)# route-map incoming permit 10Router(config-route-map)# match ip address 2Router(config-route-map)# match mpls-labelRelated Commands
maximum routes
To limit the maximum number of routes in a Virtual Private Network (VPN) routing and forwarding (VRF) instance to prevent a provider edge (PE) router from importing too many routes, use the maximum routes command in VRF configuration mode or VRF address family configuration mode. To remove the limit on the maximum number of routes allowed, use the no form of this command.
maximum routes limit {warn-threshold | warning-only}
no maximum routes
Syntax Description
Command Default
No limit is set on the maximum number of routes allowed.
Command Modes
VRF address family configuration (config-vrf-af)
VRF configuration (config-vrf)Command History
Usage Guidelines
The maximum routes command can be configured in one of two ways:
•
•
To limit the number of routes allowed in the VRF, use the maximum routes limit command with the warn-threshold argument. The warn-threshold argument generates a warning and does not allow the addition of routes to the VRF when the maximum number set by the limit argument is reached. The software generates a warning message every time a route is added to a VRF when the VRF route count is above the warning threshold. The software also generates a route rejection notification when the maximum threshold is reached and every time a route is rejected after the limit is reached.
To set a number of routes at which you receive a notification, but which does not limit the number of routes that can be imported into the VRF, use the maximum routes limit command with the warn-only keyword.
To configure the router to generate SNMP notifications (traps or informs) for these values, use the snmp-server enable traps mpls vpn command in global configuration mode.
Examples
The following example shows how to set a limit threshold of VRF routes to 1000. When the number of routes for the VRF reaches 1000, the router issues a syslog error message, but continues to accept new VRF routes.
Router(config)# ip vrf vrf1Router(config-vrf)# rd 100:1Router(config-vrf)# route-target import 100:1Router(config-vrf)# maximum routes 1000 warning-onlyThe following example shows how to set the maximum number of VRF routes allowed to 1000 and set the warning threshold at 80 percent of the maximum. When the number of routes for the VRF reaches 800, the router issues a warning message. When the number of routes for the VRF reaches 1000, the router issues a syslog error message and rejects any new routes.
Router(config)# ip vrf vrf2Router(config-vrf)# rd 200:1Router(config-vrf)# route-target import 200:1Router(config-vrf)# maximum routes 1000 80The following example for an IPv6 address family defined under the vrf definition command shows how to set the maximum number of VRF routes allowed to 500 and set the warning threshold at 50 percent of the maximum. When the number of routes for the VRF reaches 250, the router issues a warning message. When the number of routes for the VRF reaches 500, the router issues a syslog error message and rejects any new routes.
Router(config)# vrf definitionRouter(config-vrf)# address-family ipv6Router(config-router-vrf)# maximum routes 500 50Related Commands
medium p2p
To configures the interface as point-to-point, use the medium p2p command in interface configuration mode. To return the interface to its normal mode, use the no form of this command.
medium p2p
no medium p2p
Syntax Description
This command has no arguments or keywords.
Command Default
Interfaces are configured to connect to multiple devices.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
This command allows the router to send and receive all Multiprotocol Label Switching (MPLS) transport profile (TP) packets using a common multicast MAC address knowing that it is communicating with only one other device.
Examples
The following example configures the interface as point-to-point:
Router(config)# interface eth0/0Router(config-if)# medium p2pRelated Commands
metric-style narrow
To configure a router running Intermediate System-to-Intermediate System (IS-IS) so that it generates and accepts old-style type, length, and value objects (TLVs), use the metric-style narrow command in router configuration mode. To disable this function, use the no form of this command.
metric-style narrow [transition] [level-1 | level-2 | level-1-2]
no metric-style narrow [transition] [level-1 | level-2 | level-1-2]
Syntax Description
Defaults
The Multiprotocol Label Switching (MPLS) traffic engineering image generates only old-style TLVs. To do MPLS traffic engineering, a router must generate new-style TLVs that have wider metric fields.
Command Modes
Router configuration
Command History
Examples
The following example shows how to configure the router to generate and accept old-style TLVs on router level 1:
Router(config-router)# metric-style narrow level-1Related Commands
metric-style transition
Configures a router to generate both old-style and new-style TLVs.
metric-style wide
Configures a router to generate and accept only new-style TLVs.
metric-style transition
To configure a router running Intermediate System-to-Intermediate System (IS-IS) so that it generates and accepts both old-style and new-style type, length, and value objects (TLVs), use the metric-style transition command in router configuration mode. To disable this function, use the no form of this command.
metric-style transition [level-1 | level-2 | level-1-2]
no metric-style transition [level-1 | level-2 | level-1-2]
Syntax Description
level-1
(Optional) Enables this command on routing level 1.
level-2
(Optional) Enables this command on routing level 2.
level-1-2
(Optional) Enables this command on routing levels 1 and 2.
Defaults
The Multiprotocol Label Switching (MPLS) traffic engineering image generates only old-style TLVs. To do MPLS traffic engineering, a router must generate new-style TLVs that have wider metric fields.
Command Modes
Router configuration
Command History
Examples
The following example shows how to configure a router to generate and accept both old-style and new-style TLVs on router level 2:
Router(config-router)# metric-style transition level-2Related Commands
metric-style narrow
Configures a router to generate and accept old-style TLVs.
metric-style wide
Configures a router to generate and accept only new-style TLVs.
metric-style wide
To configure a router running Intermediate System-to-Intermediate System (IS-IS) so that it generates and accepts only new-style type, length, and value objects (TLVs), use the metric-style wide command in router configuration mode. To disable this function, use the no form of this command.
metric-style wide [transition] [level-1 | level-2 | level-1-2]
no metric-style wide [transition] [level-1 | level-2 | level-1-2]
Syntax Description
Defaults
The Multiprotocol Label Switching (MPLS) traffic engineering image generates only old-style TLVs. To do MPLS traffic engineering, a router must generate new-style TLVs that have wider metric fields.
Command Modes
Router configuration
Command History
Usage Guidelines
If you enter the metric-style wide command, a router generates and accepts only new-style TLVs. Therefore, the router uses less memory and other resources than it would if it generated both old-style and new-style TLVs.
This style is appropriate for enabling MPLS traffic engineering across an entire network.
Note
Examples
The following example shows how to configure a router to generate and accept only new-style TLVs on level 1:
Router(config-router)# metric-style wide level-1Related Commands
mls mpls
To enable Multiprotocol Label Switching (MPLS) recirculation, use the mls mpls command in global configuration mode. To disable MPLS recirculation, use the no form of this command.
mls mpls {recir-agg | tunnel-recir}
no mls mpls {recir-agg | tunnel-recir}
Syntax Description
recir-agg
Recirculates the MPLS aggregated-label packets (only new aggregated labels are impacted).
tunnel-recir
Recirculates the tunnel-MPLS packets.
Defaults
MPLS recirculation is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
If you do not enable tunnel-MPLS recirculation, the IPv4 and IPv4-tunneled packets that have to be labeled (for example, the packets that are encapsulated with an MPLS header) will be corrupted when they are transmitted from the Cisco 7600 series router.
Examples
The following example shows how to enable aggregated-label MPLS recirculation:
Router(config)# mls mpls recir-aggThe following example shows how to enable tunnel-MPLS recirculation:
Router(config)# mls mpls tunnel-recirThe following example shows how to disable aggregated-label MPLS recirculation:
Router(config)# no mls mpls recir-aggThe following example shows how to disable tunnel-MPLS recirculation:
Router(config)# no mls mpls tunnel-recirmls mpls (guaranteed bandwidth traffic engineering)
To configure the guaranteed bandwidth traffic engineering flow parameters globally, use the mls mpls command in global configuration mode. To return to the default settings, use the no form of this command.
mls mpls {gb-te-burst burst | gb-te-cir-ratio ratio | gb-te-dscp dscp-value [markdown] | gb-te-enable [global-pool]}
no mls mpls {gb-te-burst burst | gb-te-cir-ratio ratio | gb-te-dscp dscp-value [markdown] | gb-te-enable [global-pool]}
Syntax Description
Defaults
The default settings are as follows:
•
•
•
Command Modes
Global configuration
Command History
12.2(18)SXE
This command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
Use the mls qos map dscp-exp command to reset the Exp value of the Multiprotocol Label Switching (MPLS) packet when the out-label gets swapped.
If you do not enable tunnel-MPLS recirculation, the IPv4 and IPv4-tunneled packets that need to be labeled (for example, the packets that are encapsulated with an MPLS header) will be corrupted when they are transmitted from the Cisco 7600 series router.
Use the show erm statistics command to display the Forwarding Information Base (FIB) Ternary Content Addressable Memory (TCAM) exception status for IPv4, IPv6, and MPLS protocols.
Examples
This example shows how to specify the burst duration for the guaranteed bandwidth traffic engineering flows:
Router(config)#mls mpls gb-te-burst 2000Router(config)#This example shows how to specify the ratio for CIR policing:
Router(config)#mls mpls gb-te-ratio 30Router(config)#This example shows how to specify the DSCP map for the guaranteed bandwidth traffic engineering flows and to drop the nonconforming flows:
Router(config)#mls mpls gb-te-dscp 25 markdownRouter(config)#This example shows how to enable the guaranteed bandwidth traffic engineering flow policing:
Router(config)#mls mpls gb-te-enableRouter(config)#Related Commands
show erm statistics
Displays the FIB TCAM exception status for IPv4, IPv6, and MPLS protocols.
mls mpls (recirculation)
To enable Multiprotocol Label Switching (MPLS) recirculation, use the mls mpls command in global configuration mode. To disable MPLS recirculation, use the no form of this command.
mls mpls {recir-agg | tunnel-recir}
no mls mpls {recir-agg | tunnel-recir}
Syntax Description
recir-agg
Recirculates the MPLS aggregated-label packets (new aggregated labels are impacted only).
tunnel-recir
Recirculates the tunnel-MPLS packets.
Defaults
Disabled
Command Modes
Global configuration
Command History
12.2(18)SXE
This command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
If you do not enable tunnel-MPLS recirculation, the IPv4 and IPv4-tunneled packets that need to be labeled (for example, the packets that are encapsulated with an MPLS header) will be corrupted when they are transmitted from the Cisco 7600 series router.
Use the show erm statistics command to display the Forwarding Information Base (FIB) Ternary Content Addressable Memory (TCAM) exception status for IPv4, IPv6, and MPLS protocols.
Examples
This example shows how to enable the aggregated-label MPLS recirculation:
Router(config)#mls mpls recir-aggRouter(config)#This example shows how to enable the tunnel-MPLS recirculation:
Router(config)#mls mpls tunnel-recirRouter(config)#This example shows how to disable the aggregated-label MPLS recirculation:
Router(config)#no mls mpls recir-aggRouter(config)#This example shows how to disable the tunnel-MPLS recirculation:
Router(config)#no mls mpls tunnel-recirRouter(config)#Related Commands
show erm statistics
Displays the FIB TCAM exception status for IPv4, IPv6, and MPLS protocols.
mls mpls qos input uniform-mode
To enable Multiprotocol Label Switching (MPLS) quality of service (QoS) marking of ingress packets to be copied into the differentiated services code point (DSCP) field of the ingress packet, use the mls mpls qos input uniform-mode command in interface configuration mode. To disable the copying operation, use the no form of this command.
mls mpls qos input uniform-mode
no mls mpls qos input uniform-mode
Syntax Description
This command has no arguments or keywords.
Command Default
No marking operation is performed on the incoming packets or the GRE headers.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
This command is supported only in PFC3C mode or PFC3CXL mode.
Enter the show mls qos command to verify the configuration.
Examples
The following example shows how to enable the original QoS marking of ingress packets to be copied into the DSCP field and copied in the GRE header:
Router(config-if)# mls mpls qos input uniform-modeRelated Commands
monitor peer bfd
To enable pseudowire fast-failure detection capability in a bidirectional forwarding detection (BFD) configuration, use the monitor peer bfd command in pseudowire class configuration mode. To disable pseudowire fast-failure detection, use the no form of this command.
monitor peer bfd [local interface loopback-url]
no monitor peer bfd
Syntax Description
local interface loopback-url
(Optional) Local interface for the source address to use when locating a BFD configuration.
Command Default
Pseudowire fast-failure detection is not enabled.
Command Modes
Pseudowire class (config-pw-class)
Command History
Examples
The following example shows how to enable pseudowire fast-failure detection capability:
Router# configure terminalinterface Loopback0ip address 10.1.1.1 255.255.255.255!pseudowire-class mplsmonitor peer bfd local interface Loopback0Related Commands
mpls atm control-vc
Note
To configure the control-VC virtual path identifier (VPI) and virtual circuit identifier (VCI) values for the initial link to the Multiprotocol Label Switching (MPLS) peer, use the mpls atm control-vc command in interface configuration mode. To unconfigure the values, use the no form of this command.
mpls atm control-vc vpi vci
no mpls atm control-vc vpi vci
Syntax Description
vpi
Virtual path identifier, in the range from 0 to 4095.
vci
Virtual circuit identifier, in the range from 0 to 65535.
Defaults
0/32
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Use this command to establish the LDP session and to carry non-IP traffic. The default VPI VCI for the control VC is (0, 32). If for any reason you need to have a different control-VC, use the mpls atm control-vc command to configure any VPI VCI allowed by the vpi and vci arguments for the control VC.
Examples
The following example shows an MPLS subinterface and VPI 1 and VCI 34 as the control VCs:
Router(config)# interface atm4/0.1 mplsRouter(config-if)# mpls ipRouter(config-if)# mpls atm control-vc 1 34Related Commands
mpls atm cos
Note
To change the configured bandwidth allocation for class of service (CoS), use the mpls atm cos command in global configuration mode.
mpls atm cos {available | standard | premium | control} weight
Syntax Description
Defaults
Available 50%, control 50%
Command Modes
Global configuration (config)
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
12.4(20)T
This command was removed.
Examples
The following example shows how to configure the XTagATM interface for CoS traffic:
Router(config)# interface xtagatm12Router(config-if)# extended-port atm1/0 descriptor 1.2Router(config-if)# mpls ipRouter(config-if)# mpls atm cos available 49Router(config-if)# mpls atm cos standard 50Router(config-if)# mpls atm cos premium 0Router(config-if)# mpls atm cos control 1mpls atm disable-headend-vc
Note
To remove all headend virtual circuits (VCs) from the Multiprotocol Label Switching (MPLS) Label Switch Controller (LSC) and disable its ability to function as an edge label switch router (LSR), use the mpls atm disable-headend-vc command in global configuration mode. To restore the headend VCs of the MPLS LSC and restore full edge LSR functionality, use the no form of this command.
mpls atm disable-headend-vc
no mpls atm disable-headend-vc
Syntax Description
This command has no arguments or keywords.
Defaults
Edge LSR is enabled.
Command Modes
Global configuration (config)
Command History
12.0(7)DC
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
12.4(20)T
This command was removed.
Usage Guidelines
This command prevents the LSC from initiating headend label VCs (LVCs), and thus reduces the number of LVCs used in the network.
Examples
The following example shows how to disable the MPLS LSC from acting like an edge LSR and therefore cannot create headend LVCs:
mpls atm disable-headend-vcmpls atm multi-vc
Note
To configure a router subinterface to create one or more label virtual circuits (VCs) over which packets of different classes are sent, use the mpls atm multi-vc command in ATM subinterface submode. To remove the label virtual circuits, use the no form of this command.
mpls atm multi-vc
no mpls atm multi-vc
Syntax Description
This command has no arguments or keywords.
Command Modes
ATM subinterface submode (config-subif)
Command History
Usage Guidelines
This command is valid only on ATM MPLS subinterfaces.
Examples
The following example shows how to configure interface ATM2/0/0.1 on the networking device for MPLS quality of service (QoS) multi-VC mode:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface ATM2/0/0.1 mplsRouter(config-subif)# mpls atm multi-vcRouter(config-subif)# exitRouter(config)# exitRelated Commands
mpls atm vpi
Note
To configure the range of values to use in the virtual path identifier (VPI) field for label virtual circuits (LVCs), use the mpls atm vpi command in interface configuration mode. To clear the range of values, use the no form of this command.
mpls atm vpi vpi [- vpi] [vci-range low - high]
no mpls atm vpi vpi [- vpi] [vci-range low - high]
Syntax Description
Defaults
The default VPI range is 1-1.
The default VCI range is 33-65535.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
You might need to change the default VPI range on the switch if:
•
•
To configure ATM MPLS on a router interface (for example, an ATM Interface Processor), you must enable an MPLS subinterface.
Note
Use this command to select an alternate range of VPI values for ATM label assignment on this interface. The two ends of the link negotiate a range defined by the intersection of the range configured at each end.
•
•
•
If you use the vci-range keyword, you must specify a VPI value.
Examples
The following example shows how to create a subinterface and selects a VPI range from VPI 1 to VPI 3:
Router(config)# interface atm4/0.1 mplsRouter(config-if)# mpls ipRouter(config-if)# mpls atm vpi 1-3The following example shows how to create a subinterface with a VPI of 240 and a VCI range between 33 and 4090:
Router(config)# interface atm4/0.1 mplsRouter(config-if)# mpls ipRouter(config-if)# mpls atm vpi 240 vci-range 33-4090Related Commands
mpls atm control-vc
Configures VPI and VCI values for the initial link to an MPLS peer.
mpls atm vp-tunnel
Note
To specify an interface or a subinterface as a virtual path (VP) tunnel, use the mpls atm vp-tunnel command in interface configuration mode. To remove the VP tunnel from an interface or subinterface, use the no form of this command.
mpls atm vp-tunnel vpi [vci-range low - high]
no mpls atm vp-tunnel vpi [vci-range low - high]
Syntax Description
vpi
Virtual path identifier (VPI) value for the local end of the tunnel (0 to 4095).
vci-range low - high
(Optional) Range of virtual channel identifier (VCI) values the VP tunnel can use.
Defaults
If you do not specify a VCI range for the VP tunnel, the tunnel uses the default VCI range of 33-65535.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The mpls atm vp-tunnel and mpls atm vpi commands are mutually exclusive.
This command is available on both extended MPLS ATM (XTagATM) interfaces and on LC-ATM subinterfaces of router ATM interfaces. The command is not available on the LS1010, where all subinterfaces are automatically VP tunnels.
It is not necessary to use the mpls atm vp-tunnel command on an XTagATM interface in most applications. The switch learns (through VSI interface discovery) whether the XTagATM interface is a tunnel, the VPI value of the tunnel, and tunnel status.
Examples
The following example shows how to create an MPLS subinterface VP tunnel with a VPI value of 4:
Router(config-if)# mpls atm vp-tunnel 4The following example shows how to create a VP tunnel with a value of 240 and a VCI range of 33 to 4090:
Router(config-if)# mpls atm vp-tunnel 240 vci-range 33-4090mpls bgp forwarding
To enable an interface to receive Multiprotocol Label Switching (MPLS) packets when the signaling of MPLS labels is through the use of the Border Gateway Protocol (BGP), use the mpls bgp forwarding command in interface configuration mode. To disable this configuration, use the no form of this command.
mpls bgp forwarding
no mpls bgp forwarding
Syntax Description
This command has no arguments or keywords.
Command Default
MPLS forwarding by BGP is not enabled.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Use the mpls bgp forwarding command when you want to enable MPLS forwarding on directly connected loopback interfaces. This command is automatically generated by BGP for directly connected nonloopback neighbors.
Examples
The following example shows how to configure BGP to enable MPLS forwarding on a directly connected loopback interface, Ethernet 0/0:
interface ethernet 0/0mpls bgp forwardingRelated Commands
mpls control-word
To enable the Multiprotocol Label Switching (MPLS) control word in an Any Transport over MPLS (AToM) static pseudowire connection, use the mpls control-word command in xconnect configuration mode. To disable the control word, use the no form of this command.
mpls control-word
no mpls control-word
Syntax Description
This command has no arguments or keywords.
Command Default
The control word is included in connections.
Command Modes
Xconnect configuration
Command History
Usage Guidelines
This command is used when configuring AToM static pseudowires, and is mandatory when configuring Frame Relay data-link connection identifier (DLCI) and ATM adaptation layer 5 (AAL5) attachment circuits.
Because the control word is included by default, it may be necessary to explicitly disable this command in AToM static pseudowire configurations.
When the mpls control-word command is used in static pseudowire configurations, the command must be configured the same way on both ends of the connection to work correctly, or else the provider edge routers will not be able to exchange control messages to negotiate inclusion or exclusion of the control word.
Examples
The following example shows the configuration for both sides of an AToM static pseudowire connection:
Router# configure terminalRouter(config)# interface Ethernet 1/0Router(config-if)# xconnect 10.131.191.251 100 encapsulation mpls manual pw-class mplsRouter(config-if-xconn)# mpls label 100 150Router(config-if-xconn)# no mpls control-wordRouter(config-if-xconn)# exit
Router(config-if)# exit
Router# configure terminalRouter(config)# interface Ethernet 1/0Router(config-if)# xconnect 10.132.192.252 100 encapsulation mpls manual pw-class mplsRouter(config-if-xconn)# mpls label 150 100Router(config-if-xconn)# no mpls control-wordRouter(config-if-xconn)# exit
Router(config-if)# exit
Related Commands
mpls cos-map
Note
To create a class map that specifies how classes map to label virtual circuits (VCs) when they are combined with a prefix map, use the mpls cos-map command in global configuration mode.
mpls cos-map cos-map
Syntax Description
Defaults
No class maps are specified.
Command Modes
Global configuration (config)
Command History
Examples
The following example shows how to create a class map:
Router(config)# mpls cos-map 55Router(config-mpls-cos-map)# class 1 premiumRouter(config-mpls-cos-map)# exitRouter(config)#Related Commands
mpls cos-map
Displays the QoS map used to assign a quantity of label virtual circuits and the associated class of service for those label virtual circuits.
mpls experimental
To configure Multiprotocol Label Switching (MPLS) experimental (EXP) levels for a virtual circuit (VC) class that can be assigned to a VC bundle and thus applied to all VC members of that bundle, use the mpls experimental command in VC-class configuration mode. To remove the MPLS EXP levels from the VC class, use the no form of this command.
To configure the MPLS EXP levels for a VC member of a bundle, use the mpls experimental command in bundle-vc configuration mode. To remove the MPLS EXP levels from the VC, use the no form of this command.
mpls experimental [other | range]
no mpls experimental
Syntax Description
Defaults
Defaults to other, that is, any MPLS EXP levels in the range from 0 to 7 that are not explicitly configured.
Command Modes
VC-class configuration for a VC class (config-vc-class)
Bundle-vc configuration for ATM VC bundle members (config-if-atm-member)Command History
Usage Guidelines
Assignment of MPLS EXP levels to VC bundle members allows you to create differentiated service because you can distribute the MPLS EXP levels over the different VC bundle members. You can map a single level or a range of levels to each discrete VC in the bundle, thereby enabling VCs in the bundle to carry packets marked with different levels. Alternatively, you can configure a VC with the mpls experimental other command to indicate that it can carry traffic marked with levels not specifically configured for it. Only one VC in the bundle can be configured with the mpls experimental other command to carry all levels not specified. This VC is considered the default one.
To use this command in VC-class configuration mode, enter the vc-class atm global configuration command before you enter this command. This command has no effect if the VC class that contains the command is attached to a standalone VC, that is, if the VC is not a bundle member.
To use this command to configure an individual bundle member in bundle-VC configuration mode, first enter the bundle command to enact bundle configuration mode for the bundle to which you want to add or modify the VC member to be configured. Then use the pvc-bundle command to specify the VC to be created or modified and enter bundle-VC configuration mode.
VCs in a VC bundle are subject to the following configuration inheritance guidelines (listed in order of next highest MPLS EXP level):
•
•
•
Note
Examples
The following example configures a class named control-class that includes an mpls experimental command that, when applied to a bundle, configures all VC members of that bundle to carry MPLS EXP level 7 traffic. Note that VC members of that bundle can be individually configured with the mpls experimental command at the bundle-vc level, which would supervene.
vc-class atm control-classmpls experimental 7The following example configures a permanent virtual circuit (PVC) 401, named control-class, to carry traffic with MPLS EXP levels in the range of 4 to 2, overriding the level mapping set for the VC through VC-class configuration:
pvc-bundle control-class 401mpls experimental 4-2Related Commands
mpls export interval
To configure the collection and export of Multiprotocol Label Switching (MPLS) Prefix/Application/Label (PAL) information to a NetFlow collector, use the mpls export interval command in global configuration mode. To disable the collecting and exporting of the MPLS PAL information, use the no form of this command.
mpls export interval minutes
no mpls export interval
Syntax Description
minutes
Time interval, in minutes, between full MPLS PAL table exports. The range is from 0 to 10080.
Command Default
No capture or export of PAL table entries is configured.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use the mpls export interval command to configure the collection and export of MPLS PAL information to a NetFlow collector. The collector can be the Cisco NetFlow Collection Engine or a third-party collector application.
The minutes argument specifies the number of minutes between one export of the entire MPLS PAL table and the next export of the entire table. We recommend that you select a time interval from 360 minutes (6 hours) to 1440 minutes (24 hours) depending on the size of your network. If you want to trigger an immediate export of the PAL table, disable the functionality (no mpls export interval command) and reconfigure the command with the minutes argument greater than zero.
If you enter the command with a periodic interval of zero, entries of the MPLS PAL table are not exported repeatedly, but PAL label tracking still occurs and PAL information is exported to the collector when a label is allocated. To display the entire MPLS PAL table, use the show mpls flow mappings command.
The minutes argument that you specify is the least amount of time that passes before another export of the MPLS PAL table. The system might choose to delay the MPLS PAL table export, if the PAL export queue already contains a large number of entries. This might occur if the export queue contains tens of thousands of entries, for example, if the export occurred at a time when thousands of routes just came up, or if NetFlow did not have the time to clear the export queue from either a previous export of the full table or a previous time when thousands of routes came up in a brief period.
Examples
The following example shows how to configure a time interval of 720 minutes (12 hours) between exports of the entire MPLS PAL table to a NetFlow collector:
Router> enableRouter# configure terminalRouter(config)# mpls export interval 720Router(config)# exitRelated Commands
mpls export vpnv4 prefixes
To configure the tracking and export of VPN IPv4 (VPNv4) label information from the Multiprotocol Label Switching (MPLS) Prefix/Application/Label (PAL) table to a NetFlow collector, use the mpls export vpnv4 prefixes command in global configuration mode. To disable the tracking and exporting of VPNv4 label information, use the no form of this command.
mpls export vpnv4 prefixes
no mpls export vpnv4 prefixes
Syntax Description
This command has no arguments or keywords.
Command Default
VPNv4 labels are exported from the MPLS PAL table with a destination prefix of 0.0.0.0.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use the mpls export vpnv4 prefixes command to enable the tracking and export of VPNv4 label information from the MPLS PAL table.
In MPLS PAL table records, the default prefix stored for labels allocated by VPNs, Border Gateway Protocol (BGP) IPv4, or BGP VPNv4 is intentionally 0.0.0.0 because VPN prefixes may be reused; other VPNs may use the same prefix.
If you configure the mpls export vpnv4 prefixes command, the MPLS PAL table stores the VPN prefix and its associated route distinguisher (RD). The use of an RD removes any ambiguity among VPN prefixes. Even if IP addresses are reused, the addition of an RD creates a unique prefix.
Examples
The following example shows how to configure the tracking and exporting of VPNv4 label information from the MPLS PAL table to a NetFlow collector:
Router> enableRouter# configure terminalRouter(config)# mpls export interval 720Router(config)# mpls export vpnv4 prefixesRouter(config)# exitThe full MPLS PAL table with MPLS VPNv4 label information is configured to export to the NetFlow collector every 720 minutes (12 hours).
Related Commands
mpls export interval
Configures the collection and export of MPLS PAL information to a NetFlow collector.
show mpls flow mappings
Displays all entries in the MPLS PAL table.
mpls forwarding bgp
To enable Multiprotocol Label Switching (MPLS) nonstop forwarding on an interface that uses Border Gateway Protocol (BGP) as the label distribution protocol, use the mpls forwarding bgp command in interface configuration mode. To disable MPLS nonstop forwarding on the interface, use the no form of this command.
mpls forwarding bgp
no mpls forwarding bgp
Syntax Description
This command has no arguments or keywords.
Command Default
MPLS nonstop forwarding is not enabled on the interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
Configure this command on the interfaces of the BGP peers that send and receive labels. If this command is not configured on an interface and a stateful switchover occurs, packets received from an interface are dropped until the BGP session is established in the new route processor.
Issue this command to enable nonstop forwarding on interfaces that use BGP to distribute labels for the following types of VPNs:
•
•
Examples
In the following examples, an interface is configured to save BGP labels in the event of a stateful switchover:
Cisco 7000 Series Example
Router(config)# interface Pos1/0Router(config-if)# mpls forwarding bgpCisco 10000 Series Example
Router(config)# interface Pos1/0/0Router(config-if)# mpls forwarding bgpRelated Commands
mpls ip (global configuration)
To enable Muliprotocol Label Switching (MPLS) forwarding of IPv4 packets along normally routed paths for the platform, use the mpls ip command in global configuration mode. To disable this feature, use the no form of this command.
mpls ip
no mpls ip
Syntax Description
This command has no arguments or keywords.
Defaults
Label switching of IPv4 packets along normally routed paths is enabled for the platform.
Command Modes
Global configuration
Command History
Usage Guidelines
MPLS forwarding of IPv4 packets along normally routed paths (sometimes called dynamic label switching) is enabled by this command. For a given interface to perform dynamic label switching, this switching function must be enabled for the interface and for the platform.
The no form of this command stops dynamic label switching for all platform interfaces regardless of the interface configuration; it also stops distribution of labels for dynamic label switching. However, the no form of this command does not affect the sending of labeled packets through label switch path (LSP) tunnels.
For an LC-ATM interface, the no form of this command prevents the establishment of label virtual circuits (LVCs) originating at, terminating at, or passing through the platform.
Examples
The following example shows that dynamic label switching is disabled for the platform, and all label distribution is terminated for the platform:
Router(config)# no mpls ipRelated Commands
mpls ip (interface configuration)
Enables MPLS forwarding of IPv4 packets along normally routed paths for the associated interface.
mpls ip (interface configuration)
To enable Multiprotocol Label Switching (MPLS) forwarding of IPv4 packets along normally routed paths for a particular interface, use the mpls ip command in interface configuration mode. To disable this configuration, use the no form of this command.
mpls ip
no mpls ip
Syntax Description
This command has no arguments or keywords.
Command Default
MPLS forwarding of IPv4 packets along normally routed paths for the interface is disabled.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
MPLS forwarding of IPv4 packets along normally routed paths is sometimes called dynamic label switching. If dynamic label switching has been enabled for the platform when this command is issued on an interface, label distribution for the interface begins with the periodic transmission of neighbor discovery Hello messages on the interface. When the outgoing label for a destination routed through the interface is known, packets for the destination are labeled with that outgoing label and forwarded through the interface.
The no form of this command causes packets routed out through the interface to be sent unlabeled; this form of the command also terminates label distribution for the interface. However, the no form of the command does not affect the sending of labeled packets through any link-state packet (LSP) tunnels that might use the interface.
For an LC-ATM interface, the no form of this command prevents the establishment of label virtual circuits (LVCs) beginning at, terminating at, or passing through the interface.
Examples
The following example shows how to enable label switching on the specified Ethernet interface:
Router(config)# configure terminalRouter(config-if)# interface e0/2Router(config-if)# mpls ipRelated Commands
mpls ip default-route
To enable the distribution of labels associated with the IP default route, use the mpls ip default-route command in global configuration mode.
mpls ip default-route
Syntax Description
This command has no arguments or keywords.
Defaults
No distribution of labels for the IP default route.
Command Modes
Global configuration
Command History
Usage Guidelines
Dynamic label switching (that is, distribution of labels based on routing protocols) must be enabled before you can use the mpls ip default-route command.
Examples
The following example shows how to enable the distribution of labels associated with the IP default route:
Router# configure terminalRouter(config)# mpls ipRouter(config)# mpls ip default-routeRelated Commands
mpls ip encapsulate explicit-null
To encapsulate all packets forwarded from the interface or subinterface with an explicit NULL label header, use the mpls ip encapsulate explicit-null command in interface configuration or subinterface configuration mode. To disable this function, use the no form of this command.
mpls ip encapsulate explicit-null
no mpls ip encapsulate explicit-null
Syntax Description
This command has no arguments or keywords.
Defaults
Packets are sent out without an explicit NULL label header.
Command Modes
Interface configuration
Subinterface configurationCommand History
Usage Guidelines
This is a per-interface command. The command establishes an explicit NULL LSP at the customer edge (CE) router. If MPLS is configured on a router and you enter this command, an error message occurs. This command is also supported on the Cisco 2600 series and Cisco 3600 series platforms.
Examples
The following example shows how to encapsulate all packets forwarded onto the interface or subinterface with an explicit NULL label header:
Router(config-if)# mpls ip encapsulate explicit-nullmpls ip propagate-ttl
To control the generation of the time-to-live (TTL) field in the Multiprotocol Label Switching (MPLS) header when labels are first added to an IP packet, use the mpls ip propagate-ttl command in global configuration mode. To use a fixed TTL value (255) for the first label of the IP packet, use the no form of this command.
mpls ip propagate-ttl
no mpls ip propagate-ttl [forwarded | local]
Syntax Description
forwarded
(Optional) Prevents the traceroute command from showing the hops for forwarded packets.
local
(Optional) Prevents the traceroute command from showing the hops only for local packets.
Defaults
This command is enabled. The TTL field is copied from the IP header. A traceroute command shows all of the hops in the network.
Command Modes
Global configuration
Command History
Usage Guidelines
By default, the mpls ip propagate-ttl command is enabled and the IP TTL value is copied to the MPLS TTL field during label imposition. To disable TTL propagation for all packets, use the no mpls ip propagate-ttl command. To disable TTL propagation for only forwarded packets, use the no mpls ip propagate forwarded command. Disabling TTL propagation of forwarded packets allows the structure of the MPLS network to be hidden from customers, but not the provider.
This feature supports the IETF draft document ICMP Extensions for Multiprotocol Label Switching, draft-ietf-mpls-label-icmp-01.txt. The document can be accessed at the following URL:
http://www2.ietf.org/internet-drafts/draft-ietf-mpls-label-icmp-01.txt
Examples
The following example shows how to disable the TTL field in the MPLS header for only forwarded packets:
Router(config)# no mpls ip propagate-ttl forwardedRelated Commands
traceroute
Displays the routes that packets take through a network to their destinations.
mpls ip ttl-expiration pop
To specify how a packet with an expired time-to-live (TTL) value is forwarded, use the mpls ip ttl-expiration pop command in global configuration mode. To disable this function, use the no form of this command.
mpls ip ttl-expiration pop labels
no mpls ip ttl-expiration pop labels
Syntax Description
labels
The maximum number of labels in the packet necessary for the packet to be forwarded by means of the global IP routing table.
Defaults
The packets are forwarded by the original label stack. However, in previous versions of Cisco IOS software, the packets were forwarded by the global routing table by default.
Command Modes
Global configuration
Command History
Usage Guidelines
You can specify that the packet be forwarded by the global IP routing table or by the packet's original label stack. The forwarding method is determined by the number of labels in the packet. You specify the number of labels as part of the command. If the packet contains the same or fewer labels than you specified, it is forwarded through the use of the global IP routing table. If the packet contains more labels than you specified, the packet is forwarded through the use of the original label stack.
This command is useful if expired TTL packets do not get back to their source, because there is a break in the Interior Gateway Protocol (IGP) path. Currently, MPLS forwards the expired TTL packets by reimposing the original label stack and forwarding the packet to the end of a label switched path (LSP). (For provider edge routers forwarding traffic over a Virtual Private Network (VPN), this is the only way to get the packet back to the source.) If there is a break in the IGP path to the end of the LSP, the packet never reaches its source.
If packets have a single label, that label is usually a global address or terminal VPN label. Those packets can be forwarded through the use of the global IP routing table. Packets that have more than one label can be forwarded through the use of the original label stack. Enter the mpls ip ttl-expiration pop 1 command to enable forwarding based on more than one label. (This is the most common application of the command.)
Examples
The following example shows how to enable forwarding based on more than one label:
Router(config)# mpls ip ttl-expiration pop 1Related Commands
traceroute
Displays the routes that packets take through a network to their destinations.
mpls ipv6 source-interface
Note
Effective with Cisco IOS Release 12.4(15)T, the mpls ipv6 source-interface command is not available in Cisco IOS 12.4T releases.
To specify an IPv6 address of an interface to be used as the source address for locally generated IPv6 packets to be sent over a Multiprotocol Label Switching (MPLS) network, use the mpls ipv6 source-interface command in global configuration mode. To disable this feature, use the no form of this command.
mpls ipv6 source-interface type number
no mpls ipv6 source-interface
Syntax Description
Command Default
This command is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the mpls ipv6 source-interface command with the neighbor send-label address family configuration command to allow 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).
The mpls ipv6 source-interface command was removed from Cisco IOS software as per RFC 3484, which defines how the source address of a locally generated packet must be chosen. This command will be removed from the other Cisco IOS release trains in which it currently appears.
Examples
The following example shows loopback interface 0 being configured as a source address for locally generated IPv6 packets:
interface Loopback0ip address 192.168.99.5 255.255.255.255ipv6 address 2001:0DB8::1/32!mpls ipv6 source-interface loopback0Related Commands
neighbor send-label
Advertises the capability of the router to send MPLS labels with BGP routes.
mpls l2transport route
To enable routing of Any Transport over MPLS (AToM) packets over a specified virtual circuit (VC), use the mpls l2transport route command in the appropriate command mode. To delete the VC, use the no form of this command on both provider edge (PE) routers.
mpls l2transport route destination vc-id
no mpls l2transport route destination vc-id
Syntax Description
destination
Specifies the Label Distribution Protocol (LDP) IP address of the remote PE router.
vc-id
Assigns a VC number to the virtual circuit between two PE routers.
Defaults
Routing of MPLS packets over a specified VC is disabled.
Command Modes
Depending on the AToM transport type you are configuring, you use the mpls l2transport route command in one of the following command modes:
Command History
Usage Guidelines
A Multiprotocol Label Switching (MPLS) VC runs across an MPLS cloud to connect interfaces on two PE routers.
Use this command on each PE router to route packets across the MPLS cloud to the interface of the other PE router. Specify the LDP IP address of the other PE router for the destination parameter. Do not specify the IP address of the router from which you are issuing the command.
You can choose any number for the VC ID. However, the VC ID must be unique per pair of routers. Therefore, in large networks, it may be necessary to track the VC ID assignments to ensure that a VC ID does not get assigned twice.
Cisco 7600 Series Routers
Cisco 7600 series routers equipped with a Supervisor Engine 2 must be equipped with either an optical services module (OSM) or a FlexWAN port adapter that is facing the MPLS network with a Layer 2 Ethernet port (non-OSM) facing the customer.
The mpls l2transport route command enables the virtual connection used to route the VLAN packets. The types of virtual connections used are as follows:
•
•
During the VC setup, VC type 5 is advertised. If the peer advertises VC type 4, the VC type is changed to type 4 and the VC is restarted. The change only happens from type 5 to type 4 and never from type 4 to type 5.
An MPLS VLAN virtual circuit in Layer 2 runs across an MPLS cloud to connect the VLAN interfaces on two PE routers.
Use the mpls l2transport route command on the VLAN interface of each PE router to route the VLAN packets in Layer 2 across the MPLS cloud to the VLAN interface of the other PE router. Specify the IP address of the other PE router for the destination parameter. Do not specify the IP address of the router from which you are issuing the command.
You can choose any value for the virtual-connection ID. However, the virtual-circuit ID must be unique to each virtual connection. In large networks, you may need to track the virtual-connection ID assignments to ensure that a virtual-connection ID does not get assigned twice.
The routed virtual connections are supported on the main interfaces, not subinterfaces.
Examples
The following examples show how to enable routing of MPLS packets over a specified VC. Two routers named PE1 and PE2 establish a VC to transport packets. PE1 has IP address 172.16.0.1, and PE2 has IP address 192.168.0.1. The VC ID is 50.
ATM AAL5 over MPLS Example
At PE1, you issue the following commands:
PE1_Router(config)# interface atm5/0.100PE1_Router(config-if)# pvc 1/200PE1_Router(config-atm-vc)# encapsulation aal5PE1_Router(config-atm-vc)# mpls l2transport route 192.168.0.1 50At PE2, you issue the following commands:
PE2_Router(config)# interface atm5/0.100PE2_Router(config-if)# pvc 1/200PE2_Router(config-atm-vc)# encapsulation aal5PE2_Router(config-atm-vc)# mpls l2transport route 172.16.0.1 50ATM Cell Relay over MPLS Example
At PE1, you issue the following commands:
PE1_Router(config)# interface atm5/0.100PE1_Router(config-if)# pvc 1/200 l2transportPE1_Router(config-atm-vc)# encapsulation aal0PE1_Router(config-atm-vc)# mpls l2transport route 192.168.0.1 50At PE2, you issue the following commands:
PE2_Router(config)# interface atm5/0.100PE2_Router(config-if)# pvc 1/200 l2transportPE2_Router(config-atm-vc)# encapsulation aal0PE2_Router(config-atm-vc)# mpls l2transport route 172.16.0.1 50Ethernet over MPLS Example
At PE1, you issue the following commands:
PE1_Router(config)# interface GigabitEthernet1/0.2PE1_Router(config-subif)# encapsulation dot1Q 200PE1_Router(config-subif)# mpls l2transport route 192.168.0.1 50At PE2, you issue the following commands:
PE2_Router(config)# interface GigabitEthernet2/0.1PE2_Router(config-subif)# encapsulation dot1Q 200PE2_Router(config-subif)# mpls l2transport route 172.16.0.1 50Frame Relay over MPLS Example
At PE1, you issue the following commands:
PE1_Router(config)# connect frompls1 Serial5/0 1000 l2transportPE1_Router(config-fr-pw-switching)# mpls l2transport route 192.168.0.1 50At PE2, you issue the following commands:
PE2_Router(config)# connect frompls2 Serial2/0 102 l2transportPE2_Router(config-fr-pw-switching)# mpls l2transport route 172.16.0.1 50HDLC over MPLS Example
At PE1, you issue the following commands:
PE1_Router(config)# interface Serial3/0PE1_Router(config-if)# encapsulation hdlcPE1_Router(config-if)# mpls l2transport route 192.168.0.1 50At PE2, you issue the following commands:
PE2_Router(config)# interface Serial1/0PE2_Router(config-if)# encapsulation hdlcPE2_Router(config-if)# mpls l2transport route 172.16.0.1 50PPP over MPLS Example
At PE1, you issue the following commands:
PE1_Router(config)# interface Serial3/0PE1_Router(config-if)# encapsulation pppPE1_Router(config-if)# mpls l2transport route 192.168.0.1 50At PE2, you issue the following commands:
PE2_Router(config)# interface Serial1/0PE2_Router(config-if)# encapsulation pppPE2_Router(config-if)# mpls l2transport route 172.16.0.1 50Related Commands
show mpls l2transport vc
Displays information about AToM VCs that have been enabled to route Layer 2 packets on a router.
mpls label
To configure an Any Transport over MPLS (AToM) static pseudowire connection by defining local and remote circuit labels, use the mpls label command in xconnect configuration mode. To remove the local and remote pseudowire labels, use the no form of this command.
mpls label local-pseudowire-label remote-pseudowire-label
no mpls label
Syntax Description
Command Default
No default labels.
Command Modes
Xconnect configuration
Command History
Usage Guidelines
This command is mandatory when configuring AToM static pseudowires, and must be configured at both ends of the connection.
The mpls label command checks the validity of the local pseudowire label and will generate an error message if the label is invalid.
Examples
The following example shows configurations for both ends of an AToM static pseudowire connection:
Router# configure terminalRouter(config)# interface Ethernet 1/0Router(config-if)# no ip addressRouter(config-if)# xconnect 10.131.191.251 100 encapsulation mpls manual pw-class mplsRouter(config-if-xconn)# mpls label 100 150Router(config-if-xconn)# exit
Router(config-if)# exit
Router# configure terminalRouter(config)# interface Ethernet 1/0Router(config-if)# no ip addressRouter(config-if)# xconnect 10.132.192.252 100 encapsulation mpls manual pw-class mplsRouter(config-if-xconn)# mpls label 150 100Router(config-if-xconn)# exit
Router(config-if)# exit
Related Commands
mpls label mode
To configure per virtual routing and forwarding (VRF) labels, use the mpls label mode command in global configuration mode. To disable the configuration, use the no form of this command.
mpls label mode {vrf vrf-name | all-vrfs} protocol bgp-vpnv4 {per-prefix | per-vrf | vrf-conn-aggr}
no mpls label mode {vrf vrf-name | all-vrfs} protocol bgp-vpnv4 {per-prefix | per-vrf | vrf-conn-aggr}
Syntax Description
Command Default
Per-vrf label mode is the default for connected routes and BGP aggregate routes on the Cisco 6500 routers. Per-prefix label mode is the default for all other local routes.
Command Modes
Global configuration (config)
Command History
Examples
The following example shows how to configure all VRFs to per-vrf label mode:
Router> enableRouter# configure terminalRouter(config)# mpls label mode all-vrfs protocol bgp-vpnv4 per-vrfRelated Commands
debug ip bgp vpnv4 unicast
Displays debugging messages for VPNv4 unicast routes.
show ip vrf detail
Displays the assigned label mode for the VRF.
mpls label mode (6VPE)
To configure the MPLS VPN 6VPE per VRF Label feature, use the mpls label mode command in global configuration mode. To disable the MPLS VPN 6VPE per VRF Label feature, use the no form of this command.
mpls label mode {vrf vrf-name | all-vrfs} protocol {bgp-vpnv6 | all-afs}
{per-prefix | per-vrf}no mpls label mode {vrf vrf-name | all-vrfs} protocol {bgp-vpnv6 | all-afs}
{per-prefix | per-vrf}Syntax Description
Command Default
The command default for connected routes and Border Gateway Protocol (BGP) aggregate routes on the Cisco 7600 router is Per-vrf-aggr label mode. The command default for all other local routes is Per-prefix label mode.
Command Modes
Global configuration (config)#
Command History
Examples
The following example configures all VRFs to per-vrf mode:
Router(config)# mpls label mode all-vrfs protocol bgp-vpnv6 per-vrfRelated Commands
debug ip bgp vpnv6 unicast
Displays debugging messages for VPNv6 unicast routes.
show vrf detail
Displays the assigned label mode for the VRF.
mpls label protocol (global configuration)
To specify the Label Distribution Protocol (LDP) for a platform, use the mpls label protocol command in global configuration mode. To restore the default LDP, use the no form of this command.
mpls label protocol {ldp | tdp}
no mpls label protocol
Syntax Description
ldp
Specifies that LDP is the default label distribution protocol.
tdp
Specifies that Tag Distribution Protocol (TDP) is the default label distribution protocol.
Command Default
LDP is the default label distribution protocol.
Command Modes
Global configuration
Command History
Usage Guidelines
If neither the global mpls label protocol ldp command nor the interface mpls label protocol ldp command is used, all label distribution sessions use LDP.
Note
Examples
The following command establishes LDP as the label distribution protocol for the platform:
Router(config)# mpls label protocol ldpRelated Commands
mpls label protocol (interface configuration)
To specify the label distribution protocol for an interface, use the mpls label protocol command in interface configuration mode. To remove the label distribution protocol from the interface, use the no form of this command.
mpls label protocol {ldp | tdp | both}
no mpls label protocol
Syntax Description
Command Default
If no protocol is explicitly configured for an interface, the label distribution protocol that was configured for the platform is used. To set the platform label distribution protocol, use the global mpls label protocol command.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
To successfully establish a session for label distribution for a link connecting two label switch routers (LSRs), the link interfaces on the LSRs must be configured to use the same label distribution protocol. If there are multiple links connecting two LSRs, all of the link interfaces connecting the two LSRs must be configured to use the same protocol.
The both option is intended for use with interfaces to multiaccess networks, such as Ethernet and FDDI, where some peers might use LDP and others use TDP. When you specify the both option, the LSR sends both LDP and TDP discovery hello messages and responds to both types of messages.
Examples
The following example shows how to establish LDP as the label distribution protocol for the interface:
Router(config-if)# mpls label protocol ldpRelated Commands
show mpls interfaces
Displays information about one or more interfaces that are configured for label switching.
mpls label range
To configure the range of local labels available for use with Multiprotocol Label Switching (MPLS) applications on packet interfaces, use the mpls label range command in global configuration mode. To revert to the platform defaults, use the no form of this command.
mpls label range minimum-value maximum-value [static minimum-static-value maximum-static-value]
no mpls label range
Syntax Description
Command Default
The platform's default values are used.
Command Modes
Global configuration
Command History
Usage Guidelines
The labels 0 through 15 are reserved by the IETF (see RFC 3032, MPLS Label Stack Encoding, for details) and cannot be included in the range specified in the mpls label range command. If you enter a 0 in the command, you will get a message that indicates that the command is an unrecognized command.
The label range defined by the mpls label range command is used by all MPLS applications that allocate local labels (for dynamic label switching, MPLS traffic engineering, MPLS Virtual Private Networks (VPNs), and so on).
If you specify a new label range that does not overlap the range currently in use, the new range does not take effect until you reload the router or the router undergoes a Stateful Switchover (SSO) when you are using Cisco IOS Release 12.0S and older software. Later software with the new MPLS Forwarding Infrastructure (MFI), 12.2SR, 12.2SB, 12.2(33)XHI, 12.2(25)SE, and 12.5 allows immediate use of the new range. Existing label bindings, which may violate the newly-configured ranges, remain active until the binding is removed through other methods.
You can use label distribution protocols, such as Label Distribution Protocol (LDP) and Resource Reservation Protocol (RSVP), to reserve a generic range of labels from 16 through 1048575 for dynamic assignment.
You specify the optional keyword, static, to reserve labels for static assignment. The MPLS Static Labels feature requires that you configure a range of labels for static assignment. You can configure static bindings only from the current static range. If the static range is not configured or is exhausted, then you cannot configure static bindings.
The available range of label values is from 16 to 1048575. The maximum value defaults to 1048575, but might be limited to a lower value on certain platforms. Some platforms may support only 256,000 or 512,000 labels. Refer to your platform documentation for the default maximum label value.
If you configure the dynamic label space from 16 to 1048575, the static label space can be in a range that is outside the chosen dynamic label space. The upper and lower minimum static label values are displayed in the help line. For example, if you configure the dynamic label with a minimum value of 100 and a maximum value of 1000, the help lines display as follows:
Router(config)# mpls label range 100 1000 static ?<1001-1048575> Upper Minimum static label value<16-99> Lower Minimum static label valueReserved Label Range --> 0 to 15Available Label Range --> 16 to 1048575Dynamic Label Range --> 100 to 1000Lower End Range --> 16 to 99Upper End Range --> 1001 to 1048575In this example, you can configure a static range from one of the following ranges: 16 to 99 or 1001 to 1048575.
If the lower minimum static label space is not available, the lower minimum is not displayed in the help line. For example:
Router(config)# mpls label range 16 400 static ?<401-1048575> Upper Minimum static label valueIn this example, you can configure a static range with a minimum static value of 401 and a maximum static value of up to 1048575.
If an upper minimum static label space is not available, then the upper minimum is not displayed in the help line:
Router(config)# mpls label range 1000 1048575 static ?<16-999> Lower Minimum static label valueIn this example, the range available for static label assignment is from 16 to 999.
If you configure the dynamic label space with the default minimum (16) and maximum (1048575) values, no space remains for static label assignment, help lines are not displayed, and you cannot configure static label bindings. For example:
Router(config)# mpls label range 16 1048575 ?<cr>Examples
The following example shows how to configure the size of the local label space. In this example, the minimum static value is set to 200, and the maximum static value is set to 120000.
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# mpls label range 200 120000Router(config)#If you had specified a new range that overlaps the current range (for example, the new range of the minimum static value set to 16 and the maximum static value set to 120000), then the new range takes effect immediately.
The following example show how to configure a dynamic local label space with a minimum static value set to 1000 and the maximum static value set to 1048575 and a static label space with a minimum static value set to 16 and a maximum static value set to 999:
Router(config)# mpls label range 1000 1048575 static 16 999Router(config)#In the following output, the show mpls label range command, executed after a reload, shows that the configured range is now in effect:
Router# show mpls label rangeDownstream label pool: Min/Max label: 1000/1048575Range for static labels: Min/Max/Number: 16/999The following example shows how to restore the label range to its default value:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# no mpls label rangeRouter(config)# endRelated Commands
show mpls forwarding table
Displays the contents of the MPLS LFIB.
show mpls label range
Displays the range of the MPLS local label space.
mpls ldp address-message
To specify advertisement of platform addresses to an LC-ATM label distribution protocol (LDP) peer, use the mpls ldp address-message command in interface configuration mode. To disable this feature, use the no form of this command.
mpls ldp address-message
no mpls ldp address-message
Syntax Description
This command has no arguments or keywords.
Defaults
LDP Address and Address Withdraw messages are not sent to LC-ATM LDP peers.
Command Modes
Interface configuration
Command History
Usage Guidelines
The LDP specification includes Address and Address Withdraw messages used by a label switch router (LSR) to advertise its addresses to its peers.
An LSR uses the addresses it learns from peers when operating in Downstream Unsolicited label advertisement mode to convert between route next hop addresses (found in the LSR routing table) and peer LDP identifiers.
The ability to map between the IP address and the peer LDP identifier is required so that:
•
•
In principle, an LSR operating in Downstream On Demand (DoD) mode for an LC-ATM interface does not need this information for two reasons:
•
•
Consequently, Cisco platforms do not normally send Address and Address Withdraw messages to LC-ATM peers.
Some LDP implementations might require the information learned in Address and Address Withdraw messages for LC-ATM. The mpls ldp address-message command is provided to enable interoperability with implementation vendors that require Address messages for LC-ATM.
Note
Examples
The following is an example of the mpls ldp address-message command:
Router(config-if)# mpls ldp address-messageRelated Commands
show mpls interfaces
Displays information about one or more or all interfaces that are configured for label switching.
mpls ldp advertise-labels
To control the distribution of locally assigned (incoming) labels by means of label distribution protocol (LDP), use the mpls ldp advertise-labels command in global configuration mode. To disable this feature, use the no form of this command.
mpls ldp advertise-labels [vrf vpn-name] [interface interface | for prefix-access-list [to peer-access-list]]
no mpls ldp advertise-labels [vrf vpn-name] [interface interface | for prefix-access-list [to peer-access-list]]
Syntax Description
Defaults
The labels of all destinations are advertised to all LDP neighbors.
If the vrf keyword is not specified, this command applies to the default routing domain.
If the interface keyword is not specified, no label is advertised for the interface address.Command Modes
Global configuration
Command History
Usage Guidelines
This command is used to control which labels are advertised to which LDP neighbors. To prevent the distribution of any locally assigned labels, use the no mpls ldp advertise-labels command with no optional parameters. To reenable the distribution of all locally assigned labels to all LDP neighbors, use the mpls ldp advertise-labels command with no optional parameters.
You can execute multiple mpls ldp advertise-labels commands. In the aggregate, such commands determine how the LSR advertises local labels. The following rules describe the effects of multiple commands:
1.
2.
a.
b.
3.
a.
b.
c.
d.
e.
Note
Normally, LDP advertises labels only for IP prefixes that are in the routing table. You can use the mpls ldp advertise-labels interface command to force LDP to advertise a label for a prefix constructed from an interface address and a 32-bit mask. Such a prefix is not usually in the routing table.
Examples
In the following example, the router is configured to advertise no locally assigned labels to any LDP neighbors:
Router(config)# no mpls ldp advertise-labelsIn the following example, the router is configured to advertise to all LDP neighbors only the labels for networks 10.101.0.0 and 10.221.0.0:
Router(config)# ip access-list standard pfx-filterRouter(config-std-nacl)# permit 10.101.0.0 0.0.255.255Router(config-std-nacl)# permit 10.221.0.0 0.0.255.255Router(config-std-nacl)# exitRouter(config)# mpls ldp advertise-labels for pfx-filterRouter(config)# no mpls ldp advertise-labelsIn the following example, the router is configured to advertise the label for network 10.165.200.0 only to LSR 10.200.110.55, the label for network 10.35.35.55 only to LSR 10.150.25.25, and the labels for all other prefixes to all LSRs:
Router(config)# ip access-list standard pfx-filter1Router(config-std-nacl)# permit 10.165.200.0Router(config-std-nacl)# exitRouter(config)# ip access-list standard lsr-filter1Router(config-std-nacl)# permit 10.200.110.55Router(config-std-nacl)# exitRouter(config)# ip access-list standard pfx-filter2Router(config-std-nacl)# permit 10.35.35.55Router(config-std-nacl)# exitRouter(config)# ip access-list standard lsr-filter2Router(config-std-nacl)# permit 10.150.25.25Router(config-std-nacl)# exitRouter(config)# mpls ldp advertise-labels for pfx-filter1 to lsr-filter1Router(config)# mpls ldp advertise-labels for pfx-filter2 to lsr-filter2The output of the show mpls ip binding detail command includes the (prefix acl, peer acl) pairs that apply to each prefix. For this example, the applicable pairs are as follows:
Router# show mpls ip binding detailAdvertisement spec:Prefix acl = pfx-filter1; Peer acl = lsr-filter1Prefix acl = pfx-filter2; Peer acl = lsr-filter210.35.35.55/8, rev 109in label: 16Advertised to:10.150.25.25:0out label: imp-null lsr: 10.200.110.55:0 inuseout label: imp-null lsr: 10.150.25.25:0Advert acl(s): Prefix acl pfx-filter2, Peer acl lsr-filter210.165.200.0/8, rev 108in label: imp-nullAdvertised to:10.200.110.55:0out label: 16 lsr: 10.200.110.55:0out label: 19 lsr: 10.150.25.25:0Advert acl(s): Prefix acl pfx-filter1, Peer acl lsr-filter110.0.0.33/32, rev 98out label: imp-null lsr: 10.150.25.25:010.0.0.44/32, rev 99in label: imp-nullAdvertised to:10.200.110.55:0 10.150.25.25:010.150.25.25/32, rev 101in label: 20Advertised to:10.200.110.55:0 10.150.25.25:0out label: 19 lsr: 10.200.110.55:0out label: imp-null lsr: 10.150.25.25:0 inuse10.0.0.44/32, rev 103in label: imp-nullAdvertised to:10.200.110.55:0 10.150.25.25:0out label: 20 lsr: 10.200.110.55:0out label: 18 lsr: 10.150.25.25:010.200.110.55/32, rev 104in label: 17Advertised to:10.200.110.55:0 10.150.25.25:0out label: imp-null lsr: 10.200.110.55:0 inuseout label: 17 lsr: 10.150.25.25:0Router#In the following example, the vrf keyword is specified to configure label advertisement in the VPN routing and forwarding instance named vpn1:
Router(config)# mpls ldp advertise-labels vrf vpn1 for pfx-filter1 to lsr-filter1Router(config)# mpls ldp advertise-labels vrf vpn1 for pfx-filter2 to lsr-filter2The following example uses the interface keyword to configure label advertisement for a /32 prefix constructed from the IP address of ethernet interface 1/1:
Router(config)# mpls ldp advertise-labels interface ethernet1/1Related Commands
mpls ldp advertise-labels old-style
To cause the for prefix-access-list parameter of the mpls ldp advertise-labels command to be interpreted according to the method used in earlier Cisco IOS software versions, use the mpls ldp advertise-labels old-style command in global configuration mode. To disable this feature, use the no form of this command.
mpls ldp advertise-labels [vrf vpn-name] old-style
no mpls ldp advertise-labels [vrf vpn-name] old-style
Syntax Description
vrf vpn-name
(Optional) Specifies the VPN routing and forwarding (VRF) instance for label advertisement.
Defaults
If this command is not specified, the for prefix-access-list parameter in any mpls ldp advertise-labels commands is interpreted according to the rules specified under the "Usage Guidelines" section for the mpls ldp advertise-labels command.
If the vrf vpn-name parameter is not specified, this command applies to the default routing domain.Command Modes
Global configuration
Command History
Usage Guidelines
The method for interpreting the for prefix-access-list parameter in the mpls ldp advertise-labels command is defined by Rule 2.a in the "Usage Guidelines" section in the mpls ldp advertise-labels command. This Rule 2.a follows normal access list conventions.
However, earlier Cisco IOS software versions used a different method for interpreting the for prefix-access-list parameter in mpls ldp advertise-labels command. For those earlier software versions, Rule 2.a read as follows:
2. A given prefix can have, at most, one (prefix acl, peer acl) pair that "applies" to it.
a.
This earlier Rule 2.a departed from normal access list conventions in that:
•
•
Use the mpls ldp advertise-labels old-style command to force the use of the old-style method of interpreting the for prefix-access-list parameter used by earlier software versions if the following apply:
•
•
Examples
The following command causes the old-style method of interpreting the for prefix-access-list parameter to be used in executing mpls ldp advertise-labels commands:
Router# mpls ldp advertise-labels old-styleIn the following example, the vrf keyword is specified to configure label advertisement in the VFR instance named vpn1:
Router(config)# mpls ldp advertise-labels vrf vpn1 old-styleRelated Commands
mpls ldp advertise-labels
Controls the distribution of locally assigned labels by means of LDP.
mpls ldp atm control-mode
Note
To control the mode used for handling label binding requests on LC-ATM interfaces, use the mpls ldp atm control-mode command in global configuration mode. To disable this feature, use the no form of this command.
mpls ldp atm control-mode {ordered | independent}
no mpls ldp atm control-mode {ordered | independent}
Syntax Description
Defaults
The default is ordered control mode.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use of ordered control mode by an ATM device acting as a transit LSR in an ATM cloud ensures that the device will receive labeled packets to forward only after it has learned the outgoing labels required by MPLS to forward the packets. Ordered control mode relieves the device of the burden of reassembling cells into packets that must be forwarded by means of the normal (non-MPLS) packet forwarding or discard mechanisms.
Use of independent control mode on ATM transit LSRs might slightly reduce the time an ATM edge router must wait to use an ATM label switched path (LSP) it has initiated. Independent control mode eliminates the need for the edge router to wait for the Label Request/Label Mapping signaling to traverse the ATM cloud from edge router ingress to egress and back before it can send packets into the LSP. However, there is a risk that an ATM transit device might receive labeled packets before it has learned the outgoing labels required for MPLS forwarding, thus forcing the transit device to reassemble the cells into a packet that it is likely to discard.
Examples
In the following example, the mode for handling LDP Label Request messages is set to "independent" for the platform:
Router# mpls ldp atm control-mode independent
Feedback