To customize the default behavior of echo packets, use the
echo command in MPLS OAM configuration mode. To set the echo packet’s behavior to its default value, use the
no form of this command.
Configures the jitter value, in milliseconds, that is used in the jitter type, length, values (TLVs) and sent as part of the echo request packets. The range is from 1 to 2147483647. The default is 200.
permit
Specifies VRF instances from which to permit echo packets from.
vrf
Specifies the VRF instance where echo packet are permitted.
all
Permits echo packets on all VRF instances.
revision
Specifies the revision number of the echo packet’s default values. Valid values are:
3—draft-ietf-mpls-lsp-ping-03 (Revision 2)
4—RFC 4379 compliant (default)
vendor-extension
Sends Cisco-specific extension TLVs with the echo packets.
Command Default
Cisco-specific extension TLVs are sent with the echo packet. Revision 4 is the router’s default.
Command Modes
MPLS OAM configuration
Command History
Release
Modification
12.4(6)T
This command was introduced.
12.0(32)SY
This command was integrated into Cisco IOS Release 12.0(32)SY.
12.4(11)T
This command was integrated into Cisco IOS Release 12.4(11)T.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31)SB2.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
12.0(33)S
This command was integrated into Cisco IOS Release 12.0(33)S.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
12.2(33)SXI
This command was integrated into Cisco IOS Release 12.2(33)SXI.
15.3(3)S
This command was modified. The jitter keyword was added.
Usage Guidelines
Before you can use the
echo command, you must first enter the
mpls oam command to enter MPLS OAM configuration mode.
The jitter keyword specifies the jitter TLV that is encoded in the echo request to instruct the responder to delay responding by a random time between zero and the jitter value. This allows the echo replies to be spread out uniformly over the jitter duration. The configured jitter value is also used by the responder node. If the configured jitter value is smaller than the received jitter TLV, then the reply is generated after a random time between one and the configured jitter value. If the configured jitter value is larger than the received jitter TLV, then the reply is generated after a random time between one and the received jitter TLV.
Specify the
revision keyword if one of the following conditions exists:
You want to change the revision number from the default value of
4 to 3.
You previously entered the
mpls oam command and changed the revision number to
3 and you want to change it back to
4.
To prevent failures reported by the replying device due to TLV version issues, you can use the
echo revision command to configure all devices in the core for the same version of the IEFT label-switched path (LSP) ping draft. For example, if the network is running draft RFC 4379 implementations, but one device is capable of only Version 3 (Cisco Revision 3), configure all devices in the network to operate in Revision 3 mode. Revision 3 mode is used only with Multiprotocol Label Switching (MPLS) LSP ping or traceroute. Revision 3 mode does not support MPLS multipath LSP traceroute.
The
vendor-extension keyword is enabled by default in the device. If your network includes devices that are not Cisco devices, you may want to disable Cisco-extended TLVs. To disable Cisco-extended TLVs, specify the
no echo vendor-extension command in MPLS OAM configuration mode. To enable Cisco-extended TLVs again, enter the
echo vendor-extension command.
Examples
The following example configures the jitter value to 100 and permits echo packets on all VRFs:
Enters MPLS OAM configuration mode for customizing the default behavior of echo packets.
encapsulation (Any Transport over MPLS)
To configure the ATM adaptation layer (AAL) encapsulation for an Any Transport over MPLS (AToM), use the
encapsulation command in the appropriate configuration mode. To remove the ATM encapsulation, use the
no form of this command.
encapsulationlayer-type
noencapsulationlayer-type
Syntax Description
layer-type
The adaptation layer type, which is one of the following:
aal5--ATM adaptation layer 5
aal0--ATM adaptation layer 0
Command Default
The default encapsulation is AAL5.
Command Modes
L2transport PVC configuration--for ATM PVCs
VC class configuration--for VC class
Command History
Release
Modification
12.0(23)S
This command was introduced.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T.
12.0(30)S
This command was updated to enable ATM encapsulations as part of a virtual circuit (VC) class.
12.0(31)S
This command was integrated into Cisco IOS Release 12.0(31)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.4(11)T
This command was integrated into Cisco IOS Release 12.4(11)T.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
15.0(1)S
This command was integrated into Cisco IOS Release 15.0(1)S.
Cisco IOS XE Release 3.1S
This command was integrated into Cisco IOS XE Release 3.1S.
Usage Guidelines
In L2transport VC configuration mode, the
pvc command and the
encapsulation command work together. Use the commands for AToM differently than for all other applications. The table below shows the differences in how the commands are used.
Table 1 AToM-Specific Variations of the pvc and encapsulation Commands
pvc command: For most applications, you create a permanent virtual circuit (PVC) by using the
pvcvpi/vci command. For AToM, you must add the
l2transport keyword to the
pvc command. The
l2transport keyword enables the PVC to transport Layer 2 packets.
encapsulation command: The
encapsulation command for AToM has only two keyword values:
aal5 or
aal0. You cannot specify an encapsulation type, such as
aal5snap. In contrast, the
encapsulation aal5 command you use for most other applications requires you to specify the encapsulation type, such as
aal5snap.
You cannot create switched virtual circuits or VC bundles to transport Layer 2 packets.
When you use the
aal5 keyword, incoming cells (except Operation, Administration, and Maintenance [OAM] cells) on that PVC are treated as AAL5 encapsulated packets. The router reassembles the packet from the incoming cells. The router does not check the contents of the packet, so it does not need to know the encapsulation type (such as
aal5snap and
aal5mux). After imposing the Multiprotocol Label Switching (MPLS) label stack, the router sends the reassembled packet over the MPLS core network.
When you use the
aal0 keyword, the router strips the header error control (HEC) byte from the cell header and adds the MPLS label stack. The router sends the cell over the MPLS core network.
Examples
The following example shows how to configure a PVC to transport ATM cell relay packets for AToM:
To configure the ATM adaptation layer (AAL) for a Layer 2 local switching ATM permanent virtual circuit (PVC), use the
encapsulation command in ATM PVC L2transport configuration mode. To remove an encapsulation from a PVC, use the
no form of this command.
encapsulationlayer-type
noencapsulationlayer-type
Syntax Description
layer-type
Adaptation layer type. The values are:
aal5
aal0
aal5snap
aal5mux
aal5nlpid (not available on Cisco 12000 series)
Command Default
If you do not create a PVC, one is created for you. The default encapsulation types for autoprovisioned PVCs are as follows:
For ATM-to-ATM local switching, the default encapsulation type for the PVC is AAL0.
For ATM-to-Ethernet or ATM-to-Frame Relay local switching, the default encapsulation type for the PVC is AAL5 SNAP.
Command Modes
ATM PVC L2transport configuration
Command History
Release
Modification
12.0(27)S
This command was introduced for Layer 2 local switching.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
12.0(30)S
This command was integrated into Cisco IOS Release 12.0(30)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.4(11)T
This command was integrated into Cisco IOS Release 12.4(11)T.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
Usage Guidelines
The pvc command and the encapsulation command work together. The use of these commands with Layer 2 local switching is slightly different from the use of these commands with other applications. The following list highlights the differences:
For Layer 2 local switching, you must add the
l2transport keyword to the
pvc command. The
l2transport keyword enables the PVC to transport Layer 2 packets.
The Layer 2 local switching
encapsulation command works only with the
pvc command. You cannot create switched virtual circuits or VC bundles to transport Layer 2 packets. You can use only PVCs to transport Layer 2 packets.
The table below shows the encapsulation types supported for each transport type:
Table 2 Supported Encapsulation Types
Interworking Type
Encapsulation Type
ATM to ATM
AAL0, AAL5
ATM to Ethernet with IP interworking
AAL5SNAP, AAL5MUX
ATM to Ethernet with Ethernet interworking
AAL5SNAP
ATM to Frame-Relay
AAL5SNAP, AAL5NLPID
Examples
The following example shows how to configure a PVC to transport AAL0 packets for Layer 2 local switching:
pvc 1/100 l2transport
encapsulation aal0
Related Commands
Command
Description
pvc
Creates or assigns a name to an ATM PVC.
encapsulation dot1q
To enable IEEE 802.1Q encapsulation of traffic on a specified subinterface in a VLAN, use the
encapsulationdot1q command in interface range configuration mode or subinterface configuration mode. To disable IEEE 802.1Q encapsulation, use the
no form of this command.
Interface Range Configuration Mode
encapsulationdot1qvlan-idsecond-dot1q
{ any | vlan-id }
[native]
Virtual LAN identifier. The allowed range is from 1 to 4094. For the IEEE 802.1Q-in-Q VLAN Tag Termination feature, the first instance of this argument defines the outer VLAN ID, and the second and subsequent instances define the inner VLAN ID.
native
(Optional) Sets the VLAN ID value of the port to the value specified by the
vlan-id argument.
Note
This keyword is not supported by the IEEE 802.1Q-in-Q VLAN Tag Termination feature.
second-dot1q
Supports the IEEE 802.1Q-in-Q VLAN Tag Termination feature by allowing an inner VLAN ID to be configured.
any
Sets the inner VLAN ID value to a number that is not configured on any other subinterface.
Note
The
any keyword in the
second-dot1qcommand is not supported on a subinterface configured for IP over Q-in-Q (IPoQ-in-Q) because IP routing is not supported on ambiguous subinterfaces.
-
Separates the inner and outer VLAN ID values in the range to be defined. The hyphen is required.
,
Separates each VLAN ID range from the next range. The comma is required. Do not insert spaces between the values.
Command Default
IEEE 802.1Q encapsulation is disabled.
Command Modes
Interface range configuration (config-int-range) Subinterface configuration (config-ifsub)
Command History
Release
Modification
12.0(1)T
This command was introduced.
12.1(3)T
The
native keyword was added.
12.2(2)DD
Support was added for this command in interface range configuration mode.
12.2(4)B
This command was integrated into Cisco IOS Release 12.2(4)B.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
12.3(7)T
The
second-dot1q keyword was added to support the IEEE 802.1Q-in-Q VLAN Tag Termination feature.
12.3(7)XI1
This command was integrated into Cisco IOS Release 12.3(7)XI and implemented on the Cisco 10000 series routers.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31)SB2.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
Cisco IOS XE Release 2.2
This command was integrated into Cisco IOS XE Release 2.2.
15.2(02)SA
This command was implemented on the Cisco ME 2600X Series Ethernet Access Switches.
Usage Guidelines
Interface Range Configuration Mode
IEEE 802.1Q encapsulation is configurable on Fast Ethernet interfaces. IEEE 802.1Q is a standard protocol for interconnecting multiple switches and routers and for defining VLAN topologies.
Use the
encapsulationdot1qcommand in interface range configuration mode to apply a VLAN ID to each subinterface within the range specified by theinterfacerange command. The VLAN ID specified by the
vlan-id argument is applied to the first subinterface in the range. Each subsequent interface is assigned a VLAN ID, which is the specified
vlan-id value plus the subinterface number minus the first subinterface number (VLAN ID + subinterface number - first subinterface number).
Note
The Cisco 10000 series router does not support the
interfacerange command nor the interface range configuration mode.
Do not configure encapsulation on the native VLAN of an IEEE 802.1Q trunk without using the
native keyword. (Always use the
native keyword when
vlan-id is the ID of the IEEE 802.1Q native VLAN.)
Subinterface Configuration Mode
Use the
second-dot1q keyword to configure the IEEE 802.1Q-in-Q VLAN Tag Termination feature. 802.1Q in 802.1Q (Q-in-Q) VLAN tag termination adds another layer of 802.1Q tag (called “metro tag” or “PE-VLAN”) to the 802.1Q tagged packets that enter the network. Double tagging expands the VLAN space, allowing service providers to offer certain services such as Internet access on specific VLANs for some customers and other types of services on other VLANs for other customers.
After a subinterface is defined, use the
encapsulationdot1qcommand to add outer and inner VLAN ID tags to allow one VLAN to support multiple VLANs. You can assign a specific inner VLAN ID to the subinterface; that subinterface is unambiguous. Or you can assign a range or ranges of inner VLAN IDs to the subinterface; that subinterface is ambiguous.
Examples
The following example shows how to create the subinterfaces within the range 0.11 and 0.60 and apply VLAN ID 101 to the Fast Ethernet0/0.11 subinterface, VLAN ID 102 to Fast Ethernet0/0.12 (vlan-id= 101 + 12 - 11 = 102), and so on up to VLAN ID 150 to Fast Ethernet0/0.60 (vlan-id= 101 + 60 - 11 = 150):
Router(config)# interface range fastethernet0/0.11 - fastethernet0/0.60
Router(config-int-range)#encapsulation dot1q 101
The following example shows how to terminate a Q-in-Q frame on an unambiguous subinterface with an outer VLAN ID of 100 and an inner VLAN ID of 200:
The following example shows how to terminate a Q-in-Q frame on an ambiguous subinterface with an outer VLAN ID of 100 and an inner VLAN ID in the range from 100 to 199 or from 201 to 600:
Enables the ISL, which is a Cisco proprietary protocol for interconnecting multiple switches and maintaining VLAN information as traffic goes between switches.
encapsulationsde
Enables IEEE 802.10 encapsulation of traffic on a specified subinterface in VLANs.
interfacerange
Specifies multiple subinterfaces on which subsequent commands are executed at the same time.
showvlansdot1q
Displays information about 802.1Q VLAN subinterfaces.
encapsulation (pseudowire)
To specify an encapsulation type for tunneling Layer 2 traffic over a pseudowire, use the
encapsulation command in the appropriate configuration mode. To remove the encapsulation type, use the
no
form of this command.
encapsulation
{ mpls | udp | l2tpv2 | l2tpv3 }
noencapsulation
Syntax Description
mpls
Specifies that Multiprotocol Label Switching (MPLS) is used as the data encapsulation method.
udp
Specifies that UDP is used as the data encapsulation method.
l2tpv2
Specifies that Layer 2 Tunneling Protocol version 2 (L2TPv2) is used as the data encapsulation method.
l2tpv3
Specifies that L2TPv3 is used as the data encapsulation method.
Command Default
Encapsulation type for tunneling Layer 2 traffic is not configured.
Command Modes
Interface configuration (config-if)
Pseudowire class configuration (config-pw-class)
Template configuration (config-template)
Command History
Release
Modification
12.0(25)S
This command was introduced.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
12.2(27)SBC
This command was integrated into Cisco IOS Release 12.2(27)SBC.
15.1(2)S
This command was modified. The
udp keyword was added.
15.2(1)S
This command was modified. The
l2tpv2 and
l2tpv3 keywords were added in a release prior to Cisco IOS Release 15.2(1)S.
Cisco IOS XE Release 3.4S
This command was integrated into Cisco IOS Release XE 3.4S.
Cisco IOS XE Release 3.7S
This command was modified as part of the MPLS-based Layer 2 VPN (L2VPN) command modifications for cross-OS support. This command was made available in interface configuration and template configuration modes for MPLS encapsulation.
15.1(2)SNG
This command was integrated into Cisco ASR 901 Series Aggregation Services Routers.
15.3(1)S
This command was integrated in Cisco IOS Release 15.3(1)S.
Usage Guidelines
To change the data encapsulation method for tunneling Layer 2 traffic over a pseudowire, follow these:
Use the
no pseudowire-class command in global configuration mode to delete the pseudowire.
Use the
pseudowire-class command to reestablish the pseudowire.
Change the encapsulation method using the
encapsulation command
The following error message is displayed if you use the
no encapsulation mpls or
encapsulation (l2tpv3)
command to change encapsulation on an existing pseudowire:
Encapsulation changes are not allowed on an existing pw-class.
You must configure the
ip local interface command on the same pseudowire class to define the local IP address. All existing time-to-live (TTL) and type of service (TOS) setting values configured by the
ip ttl and
ip tos (L2TP) commands are allowed in the pseudowire class. The
ip local interface command is applicable only when L2TP and UDP data encapsulation methods are used.
Note
The
l2tpv2,
l2tpv3, and
udp keywords are not available in interface configuration and template configuration modes.
Examples
The following example shows how to configure UDP as the data encapsulation method for the pseudowire class ether-pw:
The following example shows how to configure MPLS as the data encapsulation in template configuration mode:
Device(config)# template type pseudowire template1
Device(config-template)# encapsulation mpls
Related Commands
Command
Description
ip ttl
Configures the TTL byte in the IP headers of Layer 2 tunneled packets.
ip tos (L2TP)
Configures the TOS byte in the header of Layer 2 tunneled packets.
pseudowire-class
Specifies the name of a pseudowire class and enters pseudowire class configuration mode.
xconnect
Binds an attachment circuit to an L2TPv3 pseudowire for xconnect service and enters xconnect configuration mode.
exclude-address
To exclude an address from an IP explicit path, use the
exclude-address command in global configuration mode after entering explicit path configuration mode via the
ip-explicit path command. To remove an address exclusion from an IP explicit path, use the
no index command.
exclude-addressA.B.C.D
noindexnumber
Syntax Description
A.B.C.D
Excludes an address from subsequent partial path segments. You can enter the IP address of a link or the router ID of a node.
number
Removes the specified address exclusion from an IP explicit path.
Command Default
Addresses are not excluded from an IP explicit path unless explicitly excluded by the
exclude-address command.
Command Modes
Global configuration mode
Command History
Release
Modification
12.0(14)S
This command was introduced.
12.0(14)ST
This command was integrated into Cisco IOS Release 12.0(14)ST.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
12.2(4)T2
This command was implemented on the Cisco 7500 series.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Cisco IOS XE Release 2.3
This command was implemented on the Cisco ASR 1000 Series Routers.
Usage Guidelines
An IP explicit path is a list of IP addresses, each representing a node or link in the explicit path. If you enter the
exclude-address command and specify the IP address of a link, the constraint-based Shortest Path First (SPF) routine does not consider that link when it sets up Multiprotocol Label Switching (MPLS) traffic engineering paths. If the excluded address is a flooded MPLS traffic engineering router ID, the constraint-based SPF routine does not consider that entire node. The person performing the configuration must know the router IDs of the routers because it will not be apparent whether the specified number is for a link or for a node.
Note
MPLS traffic engineering will accept an IP explicit path that comprises either all excluded addresses configured by the
exclude-address command or all included addresses configured by the
next-address command, but not a combination of both.
Examples
The following example shows how to exclude IP addresses 10.0.0.125 and 10.0.0.135 from IP explicit path 500:
To remove IP address 10.0.0.135 from the excluded addresses for explicit path 500, use the following commands:
Router(config)# ip explicit-path identifier 500
Router(cfg-ip-expl-path)# no index 1
Explicit Path identifier 500:
2: exclude-address 10.0.0.135
Router(cfg-ip-expl-path)# end
Related Commands
Command
Description
ip explicit-path
Enters the subcommand mode for IP explicit paths and creates or modifies a specified path.
exit (LSP Attributes)
To exit from the label switched path (LSP) attribute list, use the
exit command in LSP Attributes configuration mode.
exit
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
LSP Attributes configuration (config-lsp-attr)
Command History
Release
Modification
12.0(26)S
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines
Use this command after you have configured LSP-related attributes for a traffic engineering (TE) tunnel to exit the LSP attribute list and the LSP Attributes configuration mode.
Examples
The following example shows how to set up an LSP attribute list and exit the LSP Attributes configuration mode when the list is complete:
Enters address-family configuration mode to configure an EIGRP routing instance.
address-familyipv4
Enters IPv4 address family configuration mode.
address-familyipv6
Enters IPv6 address family configuration mode.
address-familynsap
Enters CLNS address family configuration mode.
address-familyvpnv4
Enters VPNv4 address family configuration mode.
address-family(VRF)
Selects an address family type for a VRF table and enters VRF address-family configuration mode.
routereigrp
Configures the EIGRP address-family process.
exp
To configure Multiprotocol Label Switching (MPLS) experimental (EXP) levels for a Frame Relay permanent virtual circuit (PVC) bundle member, use the
exp command in Frame Relay VC-bundle-member configuration mode. To remove the EXP level configuration from the PVC, use the
no form of this command.
exp
{ level | other }
noexp
Syntax Description
level
The MPLS EXP level or levels for this Frame Relay PVC bundle member. The range is from 0 to 7.
A PVC bundle member can be configured with a single level, multiple individual levels, a range of levels, multiple ranges of levels, or a combination of individual levels and level ranges.
Levels can be specified in ascending or descending order (although a subsequent
show running-configcommand will display them in ascending order).
Examples are as follows:
0
0,2,3
6-5
0-2,4-5
0,1,2-4,7
other
Specifies that this Frame Relay PVC bundle member will handle all of the remaining MPLS EXP levels that are not explicitly configured on any other bundle member PVCs.
Command Default
EXP levels are not configured.
Command Modes
Frame Relay VC-bundle-member configuration
Command History
Release
Modification
12.2(13)T
This command was introduced.
12.2(16)BX
This command was integrated into Cisco IOS Release 12.2(16)BX.
12.0(26)S
This command was integrated into Cisco IOS Release 12.0(26)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
Assignment of MPLS EXP levels to Frame Relay PVC bundle members lets you create differentiated services, because you can distribute the levels over the various PVC bundle members. You can map a single level or a range of levels to each discrete PVC in the bundle, which enables PVCs in the bundle to carry packets marked with different levels.
Use the
exp other command to indicate that a PVC can carry traffic marked with EXP levels not specifically configured for other PVCs. Only one PVC in the bundle can be configured using the
exp other command.
All EXP levels must be accounted for in the PVC bundle configuration, or the bundle will not come up. However, a PVC can be a bundle member but have no EXP level associated with it. As long as all valid EXP levels are handled by other PVCs in the bundle, the bundle can come up, but the PVC that has no EXP level configured will not participate in it.
The
exp command is available only when MPLS is configured on the interface with the
mpls ip command.
You can overwrite the EXP level configuration on a PVC by reentering the
exp command with a new value.
The MPLS experimental bits are a bit-by-bit copy of the IP precedence bits. When Frame Relay PVC bundles are configured for IP precedence and MPLS is enabled, the
precedence command is replaced by the
exp command. When MPLS is disabled, the
exp command is replaced by the
precedence command.
Examples
The following example shows the configuration of four Frame Relay PVC bundle members in PVC bundle bundle1 configured with MPLS EXP level support:
interface serial 0.1 point-to-point
encapsulation frame-relay
ip address 10.1.1.1
mpls ip
frame-relay vc-bundle bundle1
pvc 100 ny-control
class control
exp 7
protect vc
pvc 101 ny-premium
class premium
exp 6-5
protect group
no bump traffic
bump explicit 7
pvc 102 my-priority
class priority
exp 4-2
protect group
pvc 103 ny-basic
class basic
exp other
protect group
Related Commands
Command
Description
bump
Configures the bumping rules for a specific PVC member of a bundle.
class
Associates a map class with a specified DLCI.
dscp (Frame Relay VC-bundle-member)
Configures the DSCP value or values for a Frame Relay PVC bundle member.
match
Specifies which bits of the IP header to use for mapping packet service levels to Frame Relay PVC bundle members.
mpls ip
Enables label switching of IPv4 packets on an interface.
precedence (Frame Relay VC-bundle-member)
Configures the precedence levels for a Frame Relay PVC bundle member.
protect
Configures a Frame Relay PVC bundle member with protected group or protected PVC status.
export map
To associate an export map with a VPN Routing and Forwarding (VRF) instance, use the
export map command in IP VRF configuration or in VRF address family configuration mode. To remove the export map, use the
no form of this command.
exportmapmap-name
noexportmapmap-name
Syntax Description
map-name
Identifies the route map to be used as an export map.
Command Default
No export maps are associated with a VRF instance.
Command Modes
IP VRF configuration (config-vrf)
VRF address family configuration (config-vrf-af)
Command History
Release
Modification
12.0(5)T
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Cisco IOS XE Release 3.1S
This command was integrated into Cisco IOS XE Release 3.1S.
Usage Guidelines
The
export map command is used to associate a route map with the specified VRF. The export map is used to filter routes that are eligible for export out of a VRF, based on the route target extended community attributes of the route. Only one export route map can be configured for a VRF.
An export route map can be used when an application requires finer control over the routes that are exported out of a VRF than the control that is provided by import and export extended communities configured for the importing and exporting VRFs.
You can access the
export map command by using the
ip vrf global configuration command. You can also access the
export map command by using the
vrf definition global configuration command followed by the
address-family VRF configuration command.
Examples
In the following example, an export map is configured under the VRF, and an access list and route map are configured to specify which prefixes are exported:
Router(config)# ip vrf RED
Router(config-vrf)# rd 1:1
Router(config-vrf)# export map BLUE
Router(config-vrf)# route-target import 2:1
Router(config-vrf)# exit
Router(config)# access-list 1 permit 192.168.0.0 0.0.255.255
Router(config)# route-map BLUE permit 10
Router(config-route-map)# match ip address 1
Router(config-route-map)# set extcommunity rt 2:1
Router(config-route-map)# end
Related Commands
Command
Description
address-family (VRF)
Selects an address family type for a VRF table and enters VRF address family configuration mode.
import map
Configures an import route map for a VRF.
ip extcommunity-list
Creates an extended community list for BGP and controls access to it.
ip vrf
Configures a VRF routing table.
route-target
Creates a route-target extended community for a VRF.
show ip vrf
Displays the set of defined VRFs and associated interfaces.
vrf definition
Configures a VRF routing table instance and enters VRF configuration mode.
extended-port
Note
Effective with Cisco IOS Release 12.4(20)T, the
extended-port command is not available in Cisco IOS software.
To associate the currently selected extended Multiprotocol Label Switching (MPLS) ATM (XTagATM) interface with a particular external interface on the remotely controlled ATM switch, use the
extended-port command in interface configuration mode.
Identifies the ATM interface used to control the remote ATM switch. You must configure Virtual Switch Interface (VSI) on this interface using the
label-control-protocol interface configuration command.
bpxbpx-port-number
Specifies the associated Cisco BPX interface using the native BPX syntax.
>slot.port [.>virtual port ]
You can use this form of the command only when the controlled switch is a Cisco BPX switch.
descriptorvsi-descriptor
Specifies the associated port by its VSI physical descriptor. The
>vsi-descriptor string must match the corresponding VSI physical descriptor.
vsivsi-port-number
Specifies the associated port by its VSI port number. The
vsi-port-number string must match the corresponding VSI physical port number.
Command Default
Extended MPLS ATM interfaces are not associated.
Command Modes
Interface configuration (config-if)
Command History
Release
Modification
12.0(3)T
This command was introduced.
12.4(20)T
This command was removed.
Usage Guidelines
The
extended-port interface configuration command associates an XTagATM interface with a particular external interface on the remotely controlled ATM switch. The three alternate forms of the command permit the external interface on the controlled ATM switch to be specified in three different ways.
Examples
The following example shows how to associate an extended MPLS ATM interface and bind it to BPX port 2.3:
The following example shows how to associate an extended MPLS ATM interface and binds it to port 1622:
ATM(config)# interface XTagATM1622
ATM(config-if)# extended-port atm0/0 vsi 0x00010614
Related Commands
Command
Description
interfaceXTagATM
Enters interface configuration mode for an extended MPLS ATM (XTagATM) interface.
show controller vsi status
Displays a summary of each VSI-controlled interface.
flow-label enable
To enable the imposition and disposition of flow labels for a pseudowire for virtual private LAN services (VPLS), use the
flow-label enable command in pseudowire-class configuration mode. To disable the imposition and disposition of flow labels, use the
no form of this command.
flow-labelenable
noflow-labelenable
Syntax Description
This command has no arguments or keywords.
Command Default
Flow labels are not enabled.
Command Modes
pseudowire-class (config-pw-class)
Command History
Release
Modification
12.2(33)SXI4
This command was introduced.
15.1(1)SY
This command was integrated into Cisco IOS Release 15.1(1)SY.
Usage Guidelines
This command enables flow labels. MPLS adds flow labels to the label stack because they contain the flow information of a VC.
Examples
The following example configures a pseudowire and enables flow labels:
Enables load balancing of traffic across multiple core interfaces using equal cost multipaths (ECMP) for virtual private LAN services (VPLS).
forward permit l2protocol all
To define the pseudowire that is used to transport bridge protocol data unit (BPDU) information between two network provider edge (N-PE) routers, use the
forward permit l2protocol all command in L2 VFI configuration mode. To remove the pseudowire, use the
no form of this command.
forwardpermitl2protocolall
noforwardpermitl2protocolall
Command Default
The pseudowire between the two N-PE routers is not defined.
Command Modes
L2 VFI configuration (config-vfi)
Command History
Release
Modification
12.2(33)SRC
This command was introduced as part of the hierarchical virtual private LAN service (H-VPLS) N-PE Redundancy for QinQ and Multiprotocol Label Switching (MPLS) Access feature.
12.2(50)SY
This command was integrated into Cisco IOS Release 12.2(50)SY.
Cisco IOS XE Release 3.2S
This command was integrated into a release prior to Cisco IOS XE Release 3.2S.
Cisco IOS XE Release 3.6S
In Cisco IOS XE Release 3.6S, support was added for the Cisco ASR 903 Router.
Cisco IOS XE Release 3.7S
This command was modified as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support.
15.3(1)S
This command was integrated in Cisco IOS Release 15.3(1)S.
Usage Guidelines
Use the
l2vpn vfi context command or
l2 vfi
command to enter L2 VFI configuration mode. Only one pseudowire between the two N-PE routers is allowed.
Examples
The following example shows how to create a VPLS pseudowire between the two N-PE routers:
Device(config)# l2 vfi vfi1 manual
Device(config-vfi)# vpn id 20
Device(config-vfi)# forward permit l2protocol all
Device(config-vfi)# neighbor 10.10.10.10 encapsulation mpls
Device(config)# l2vpn vfi context vfi1
Device(config-vfi)# vpn id 20
Device(config-vfi)# forward permit l2protocol all
Device(config-vfi)# member 10.10.10.10 encapsulation mpls
Related Commands
Command
Description
member (l2vpn vfi)
Specifies the routers that should form a point-to-point L2VPN VFI connection.
neighbor (L2VPN Pseudowire Switching)
Specifies the routers that should form a point-to-point Layer 2 VFI connection.
show vfi
Displays information related to the VFI.
vpn id
Sets or updates a VPN ID on a VRF instance.
import map
To configure an import route map for a Virtual Private Network (VPN) routing and forwarding (VRF) instance, use the
import map command in VRF configuration or in VRF address family configuration mode. To remove the import map, use the
no form of this command.
(Optional) Specifies that IPv4 prefixes will be imported.
unicast
(Optional) Specifies that unicast prefixes will be imported.
multicast
(Optional) Specifies that multicast prefixes will be imported.
prefix-limit
(Optional) Limits the number of prefixes that will be imported. The default limit is 1000 prefixes. The range is from 1 to 2147483647 prefixes.
map-name
Identifies the route map to be used as an import route map for the VRF.
Command Default
A VRF has no import route map unless one is configured using the
import map command.
Command Modes
VRF configuration (config-vrf)
VRF address family configuration (config-vrf-af)
Command History
Release
Modification
12.0(5)T
This command was introduced.
12.0(21)ST
This command was integrated into Cisco IOS 12.0(21)ST.
12.0(22)S
This command was integrated into Cisco IOS 12.0(22)S.
12.0(23)S
This command was integrated into Cisco IOS 12.0(23)S.
12.2(13)T
This command was integrated into Cisco IOS 12.2(13)T.
12.2(14)S
This command was integrated into Cisco IOS 12.2(14)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Cisco IOS XE Release 3.1S
This command was integrated into Cisco IOS XE Release 3.1S.
15.2(2)SNG
This command was integrated into Cisco ASR 901 Series Aggregation Services Routers.
Usage Guidelines
Use an import route map when an application requires finer control over the routes imported into a VRF than provided by the import and export extended communities configured for the importing and exporting VRF. You can also use the
import map command to implement the BGP Support for IP Prefix Import from Global Table into a VRF Table feature.
The
import map command associates a route map with the specified VRF. You can use a route map to filter routes that are eligible for import into a VRF, based on the route target extended community attributes of the route. The route map might deny access to selected routes from a community that is on the import list.
The
import map command does not replace the need for a route-target import in the VRF configuration. You use the
import map command to further filter prefixes that match a route-target import statement in that VRF.
You can access the
import map command by using the
ip vrf global configuration command. You can also access the
import map command by using the
vrf definition global configuration command followed by the
address-family VRF configuration command.
Examples
The following example shows how to configure an import route map for a VRF:
Router(config)# ip vrf vrf1
Router(config-vrf)# import map importmap1
Related Commands
Command
Description
address-family (VRF)
Selects an address family type for a VRF table and enters VRF address family configuration mode.
export map
Exports IP prefixes from a VRF table into the global table.
ip vrf
Configures a VRF routing table.
route-target
Creates a route-target extended community for a VRF.
show ip vrf
Displays the set of defined VRFs and associated interfaces.
vrf definition
Configures a VRF routing table instance and enters VRF configuration mode.
index
To insert or modify a path entry at a specific index, use the
index command in IP explicit path configuration mode. To remove the path entry at the specified index, use the
no form of this command.
indexindexcommand
noindexindex
Syntax Description
index
Index number at which the path entry will be inserted or modified. Valid values are from 0 to 65534.
command
An IP explicit path configuration command that creates or modifies a path entry. (You can use only the
next-address command.)
Command Default
This command is disabled.
Command Modes
IP explicit path configuration
Command History
Release
Modification
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T.
12.0(10)ST
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Examples
The following example shows how to insert the next address at index 6:
Inserts the new path entry after the specified index number. Commands might be renumbered as a result.
interface fastethernet
Enters the command mode for IP explicit paths and creates or modifies the specified path.
list
Displays all or part of the explicit paths.
next-address
Specifies the next IP address in the explicit path.
show ip explicit-paths
Displays the configured IP explicit paths.
instance (VLAN)
To map a VLAN or a group of VLANs to a multiple spanning tree (MST) instance, use the
instance command in MST configuration mode. To return the VLANs to the default internal spanning tree (CIST) instance, use the
no form of this command.
instanceinstance-idvlansvlan-range
noinstanceinstance-id
Syntax Description
instance-id
Instance to which the specified VLANs are mapped; valid values are from 0 to 4094.
vlansvlan-range
Specifies the number of the VLANs to be mapped to the specified instance; valid values are from 1 to 4094.
Command Default
No VLANs are mapped to any MST instance (all VLANs are mapped to the CIST instance).
Command Modes
MST configuration mode (config-mst)
Command History
Release
Modification
12.2(14)SX
Support for this command was introduced on the Supervisor Engine 720.
12.2(17d)SXB
Support for this command on the Supervisor Engine 2 was extended to Cisco IOS Release 12.2 (17d)SXB.
12.2(18)SXF
This command was changed as follows:
You can configure up to 65 interfaces.
You can designate the
instance-id from 1 to 4094.
Cisco IOS XE Release XE 3.7S
This command was integrated into Cisco IOS XE Release XE 3.7S.
Usage Guidelines
The
vlansvlan-range is entered as a single value or a range.
The mapping is incremental, not absolute. When you enter a range of VLANs, this range is added or removed to the existing instances.
Any unmapped VLAN is mapped to the CIST instance.
Examples
The following example shows how to map a range of VLANs to instance 2:
The following example shows how to move a range of VLANs from instance 2 to the CIST instance:
Device(config-mst)# no instance 2 vlans 40-60
Device(config-mst)#
The following example shows how to move all the VLANs that are mapped to instance 2 back to the CIST instance:
Device(config-mst)# no instance 2
Device(config-mst)#
Related Commands
Command
Description
name(MSTconfigurationmode)
Sets the name of an MST region.
revision
Sets the revision number for the MST configuration.
show
Verifies the MST configuration.
showspanning-treemst
Displays the information about the MST protocol.
spanning-treemistconfiguration
Enters MST configuration mode.
inter-as-hybrid
To specify a Virtual Private Network (VPN) routing and forwarding (VRF) instance as an Option AB VRF, use the
inter-as-hybrid command in VRF address family configuration mode. The Inter-AS Option AB feature is a hybrid of Inter-AS Option (10)A and Inter-AS Option (10)B network configurations, enabling the interconnection of different autonomous systems to provide VPN services. To remove the configuration, use the
no form of this command.
inter-as-hybrid [csc]
[ next-hop
{ ip-address | global } ]
nointer-as-hybrid
Syntax Description
csc
(Optional) Allocates a per-prefix label for imported routes. For routes received from Option AB peers that are imported into the VRF, the learned out label is installed in forwarding. The Carrier Supporting Carrier (CSC) is a hierarchical VPN model that allows small service providers, or customer carriers, to interconnect their IP or MPLS networks over an MPLS backbone.
next-hop
(Optional) Specifies the next-hop IP address to be set on paths that are imported into the VRF and that are received from an Option AB peer. The next-hop context is also set to the VRF, which imports these paths. If the
next-hop keyword is not used, the received next hop is retained but the next-hop context (for paths received from Option AB peers) is still set to that of the VRF.
ip-address
(Optional) The IP address of the Inter-AS AB neighbor.
global
(Optional) Enables Inter-AS Option AB+. Specifies that the next-hop address for Border Gateway Protocol (BGP) updates to be set on paths that are imported to the VRF and that are received from an Option AB+ peer are placed in the global routing table. In this situation, the address used is the address of the interface that is at the remote end of the external BGP (eBGP) global shared link. The next-hop context is retained as global and not modified to that of the importing VRF.
Command Default
No VRF is specified as an Option AB VRF.
Command Modes
VRF address family configuration (config-vrf-af)
Command History
Release
Modification
12.2(33)SRC
This command was introduced.
15.0(1)M
This command was integrated into Cisco IOS Release 15.0(1)M.
15.0(1)S
This command was integrated into Cisco IOS Release 15.0(1)S.
Cisco IOS XE Release 3.1S
This command was integrated into Cisco IOS XE Release 3.1S.
15.0(1)SY
This command was modified. The
global keyword was added.
Usage Guidelines
Routes imported to this VRF can be advertised to Option AB or Option AB+ peers and VPNv4 Interior Border Gateway Protocol (iBGP) peers. When routes are received from Option AB or Option AB+ peers and imported into the VRF, the next-hop table ID of the route is set to the table ID of the VRF.
The following usage guidelines apply to the
csc keyword:
If the
csc keyword is not used, a per-VRF label is allocated for imported routes. For routes received from Option AB+ peers that are imported into the VRF, the learned out label is not installed in forwarding.
If the
csc keyword is used, when routes are received from Option AB or Option AB+ peers and are imported into the VRF, the learned out label is installed in forwarding..
The
csc and the
global keywords are mutually exclusive.
Examples
The following example shows how to configure a VRF as an Option AB VRF:
Selects an address family type for a VRF table and enters VRF address family configuration mode.
neighbor inter-as-hybrid
Configures the eBGP peer router (ASBR) as an Inter-AS Option AB peer.
rd
Creates routing and forwarding tables for a VPN.
route-target
Creates a route-target extended community for a VRF.
vrf definition
Configures a VRF routing table instance and enters VRF configuration mode.
interface auto-template
To create the template interface, use the
interface auto-template command in global configuration mode. To delete this interface, use the
no form of this command.
interfaceauto-templateinterface-num
nointerfaceauto-template
Syntax Description
interface-num
Interface number. Valid values are from 1 to 25.
Command Default
No default behavior or values are required to create templates.
Command Modes
Global configuration (config)#
Command History
Release
Modification
12.0(27)S
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines
The space before the
interface-num argument is optional.
Use the
shutdown command to disable mesh tunnel interface creation when creating a template.
Examples
The following example shows how to create template interface 1:
Router(config)# interface auto-template 1
Related Commands
Command
Description
clear mpls traffic-eng auto-tunnel mesh
Removes all the mesh tunnel interfaces and re-creates them.
mpls traffic-eng auto-tunnel mesh
Enables autotunnel mesh groups globally.
show mpls traffic-eng auto-tunnel mesh
Displays the cloned mesh tunnel interfaces of each autotemplate interface and the current range of mesh tunnel interface numbers.
interface tunnel-tp
To create a Multiprotocol Label Switching (MPLS) transport profile (TP) tunnel and configure its parameters, use the interfacetunnel-tpcommand in global configuration mode. To remove the MPLS-TP tunnel, use the no form of the command.
interfacetunnel-tpnumber
nointerfacetunnel-tpnumber
Syntax Description
number
The number of the MPLS-TP tunnel.
Command Default
No MPLS-TP tunnel parameters are configured.
Command Modes
Global configuration (config)
Command History
Release
Modification
15.1(1)SA
This command was introduced.
15.1(3)S
This command was integrated.
Usage Guidelines
Use this command on endpoint routers to specify the parameters of the MPLS-TP tunnel.
This command also enters interface configuration mode (config-if). From that mode, you can configure the following MPLS-TP parameters:
Command
Description
bfdbfd-template
The Bidirectional Forwarding Detection (BFD) template for the tunnel.
If the BFD template for an MPLS-TP tunnel is updated after the tunnel is brought up, a BFD session is brought up on both the working and, if configured, the protect LSPs.
If the BFD template for a tunnel is changed, the BFD sessions for the working and protect LSPs is brought down and then brought back up with the new BFD template.
If a BFD template is not configured on an MPLS-TP tunnel, the initial LSP state will be DOWN.
protect-lsp
Enters protect LSP interface configuration mode (config-if-protect). From this mode, you can configure the following parameters:
Incoming label (in-labelnum).
Lock (lockout)
Number of the protect LSP (lsp-number). By default, the protect LSP number is 1.
Outgoing label and link numbers (out-labelnumout-linknum)
A protect LSP is a backup for a working LSP. If the working LSP fails, traffic is switched to the protect LSP until the working LSP is restored, at which time forwarding reverts back to the working LSP.
You can lock out traffic on either the working LSP or the protect LSP but not both. When traffic is locked out of the working or protect LSP, no traffic is forwarded on that LSP.
The lock out of the LSP is signaled from one endpoint to the other. When one end has locked out one LSP, the other end may only lock out the same LSP. It is strongly advised to lock out the LSP from both ends, so that both sides know (locally) that the LSP is locked out in the absence of further signaling, which may be the case if connectivity of the LSP is broken due to maintenance for an extended time. In the absence of connectivity, a single-ended lock out expires at the remote end in under 15 minutes (256 * 3.5 seconds).
protection trigger
[ais | ldi | lkr
(Optional) Specifies protection triggers for Alarm Indication Signal (AIS), Link Down Indication (LDI), Lock Report (LKR) messages.
These triggers should be used in rare cases. They allow you to specify which of these fault notifications can trigger a protection switch. The default is to inherit the setting of the similar commands from the global settings of the protection trigger. This command allows a tunnel to override the global settings. The default for the global settings is that protection is triggered on receipt of LDI and LKR, but not AIS. (AIS is a nonfatal indication of potential issues, which turns into LDI when it is known to be fatal.)
This command is useful when other devices send AIS or LDI in unexpected ways. For example, a device from another vendor sends AIS when there are link failures and never sends AIS with the LDI flag. In that case, you can configure the protectiontriggerais command.
If a device sends LDI when there is no actual failure, but there is a possible failure, and you want BFD to detect the actual failure and cause protection switching, you can configure the noprotectiontriggerldi command.
To undo these configuration settings and resume inheriting the global settings, enter the defaultprotectiontrigger
[ais | ldi | lkr]
command.
tp bandwidth num
(Optional) Transmit bandwidth, in kilobytes. Range: 1 to 10000000. Default: 0.
With MPLS-TP, you cannot use the bandwidth command in interface configuration mode. You must use the tpbandwidth command.
tpdestinationnode-id[tunnel-tpnum] [global-idnum]
Destination MPLS-TP node ID.
global-idnum:(Optional)The global ID used for the remote end of this MPLS-TP tunnel
Range: 0 to 2147483647. Default: The global ID that is configured with the mplstp command.
tunnel-tpnum:(Optional)The tunnel-TP number of the MPLS-TP tunnel destination. If the tunnel-TP number is not specified, the number assigned to the local tunnel is used.
tp source node-idglobal-idnum
(Optional) Source MPLS-TP tunnel node ID. This is the ID of the endpoint router being configured. You can specify the source ID to override the router ID configured in the global MPLS-TP configuration.
global-idnum:(Optional) The global ID of the local endpoint for this tunnel.
Range: 0 to 2147483647. Default: The global ID that is configured with the mplstp command.
The tpsource command is optional and not typically used, because the global router ID and global ID can be used to identify the tunnel source at the endpoint. All tunnels on the router generally use the same (globally specified) source information.
tptunnel-namename
(Optional) Specifies the name of the MPLS-TP tunnel. The TP tunnel name is displayed in showmplstptunnelcommand output. This command is useful for consistently identifying the tunnel at all endpoints and midpoints.
working-lsp
Enters working LSP interface configuration mode (config-if-working). From this mode, you can configure the following parameters:
Incoming label (in-labelnum).
Lock (lockout).
Number of the working LSP (lsp-number). By default, the working LSP number is 0.
Outgoing label and link numbers (out-labelnumout-linknum)
A working LSP is the primary LSP. If the working LSP fails, traffic is switched to the protect LSP until the working LSP is restored, at which time forwarding reverts back to the working LSP.
The lock out of the LSP is signaled from one endpoint to the other. When one end has locked out one LSP, the other end may only lock out the same LSP. It is strongly advised to lock out the LSP from both ends, so that both sides know (locally) that the LSP is locked out in the absence of further signaling, which may be the case if connectivity of the LSP is broken due to maintenance for an extended time. In the absence of connectivity, a single-ended lock out expires at the remote end in under 15 minutes (256 * 3.5 seconds).
Examples
The following example specifies the parameters for an MPLS-TP tunnel:
Specifies global values used across the MPLS TP implementation and applies to all tunnels and midpoint LSPs.
mpls tp link
Specifies the parameters for an MPLS TP link.
mplstplsp
Specifies the parameters for forwarding of a MPLS-TP LSP at the tunnel midpoint.
working-lsp
Enters working Label Switched Path (LSP) mode on a TP tunnel interface.
interface virtual-ethernet
To create a virtual Ethernet interface, use the
interface virtual-ethernet command in privileged EXEC configuration mode. To remove the virtual Ethernet interface, use the
no form of this command.
interfacevirtual-ethernetnum
nointerfacevirtual-ethernetnum
Syntax Description
num
Specifies a unique number assigned to the virtual Ethernet interface. Valid values are 0 to 4094.
Command Default
Virtual Ethernet interfaces are not created.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.2(33)SXI4
This command was introduced.
15.1(1)SY
This command was integrated into Cisco IOS Release 15.1(1)SY.
Usage Guidelines
This command allows several ethernet virtual circuits (EVCs) to be bundled over a single pseudowire. The pseudowire terminating at this virtual Ethernet interface acts like a virtual ethernet trunk port. This allows Layer 2 protocols to be run over the pseudowire. Similar to a physical Ethernet interface, a virtual Ethernet interface allows configuration of Ethernet flow points.
Examples
The following example creates a virtual Ethernet interface:
Router(config)# interface virtual-ethernet 1
Related Commands
Command
Description
show interface virtual-ethernet
Displays the status of virtual Ethernet interfaces.
interface xtagatm
Note
Effective with Cisco IOS Release 12.4(20)T, the
interface xtagatm command is not available in Cisco IOS software.
To create an extended Multiprotocol Label Switching (MPLS) ATM (XTagATM) interface, use the
interface xtagatm command in global configuration mode.
interfacextagatminterface-number
Syntax Description
interface-number
The interface number.
Command Default
XTagATM interfaces are not created.
Command Modes
Global configuration (config)
Command History
Release
Modification
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.
Usage Guidelines
XTagATM interfaces are virtual interfaces that are created on reference-like tunnel interfaces. An XTagATM interface is created the first time the
interface xtagatm command is issued for a particular interface number. These interfaces are similar to ATM interfaces, except that the former only supports LC- ATM encapsulation.
Examples
The following example shows how to create an XTagATM interface with interface number 62:
Router(config)# interface xtagatm62
Related Commands
Command
Description
extended-port
Associates the currently selected extended XTagATM interface with a remotely controlled switch.
interworking
To enable Layer 2 VPN (L2VPN) interworking, use the
interworking command in pseudowire class configuration or xconnect configuration mode. To disable L2VPN interworking, use the
no form of this command.
interworking
{ ethernet | ip | vlan }
nointerworking
{ ethernet | ip | vlan }
Syntax Description
ethernet
Causes Ethernet frames to be extracted from the attachment circuit and sent over the pseudowire. It is assumed that Ethernet has end-to-end transmission. Attachment circuit frames that do not contain Ethernet frames are dropped. In the case of VLAN, the VLAN tag is removed, which leaves a pure Ethernet frame.
ip
Causes IP packets to be extracted from the attachment circuit and sent over the pseudowire. The attachment circuit frames that do not contain IPv4 packets are dropped.
vlan
Causes Ethernet frames and the VLAN tag to be sent over the pseudowire. It is assumed that Ethernet has end-to-end transmission. The attachment circuit frames that do not contain Ethernet frames are dropped.
Command Default
L2VPN interworking is disabled.
Command Modes
Pseudowire class configuration (config-pw-class)
Xconnect configuration (config-xconnect)
Command History
Release
Modification
12.0(26)S
This command was introduced.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.4(11)T
This command was integrated into Cisco IOS Release 12.4(11)T.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.2(52)SE
This command was modified. The
vlan keyword was added as part of the L2VPN Interworking: VLAN Enable/Disable Option feature.
12.2(33)SRE
This command was modified. The
vlan keyword was added as part of the L2VPN Interworking: VLAN Enable/Disable Option feature.
Cisco IOS XE Release 3.3S
This command was integrated into Cisco IOS XE Release 3.3S.
Cisco IOS XE Release 3.7S
This command was modified as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command was made available in xconnect configuration mode.
Usage Guidelines
The table below shows which L2VPN interworking features support Ethernet, IP, and VLAN types of interworking.
Table 3 L2VPN Interworking Feature Support
L2VPN Interworking Feature
Interworking Support
Frame Relay to PPP
IP
Frame Relay to ATM AAL5
IP
Ethernet/VLAN to ATM AAL5
IP and Ethernet
Ethernet/VLAN to Frame Relay
IP and Ethernet
Ethernet/VLAN to PPP
IP
Ethernet to VLAN
IP, Ethernet, and VLAN
L2VPN Interworking: VLAN Enable/Disable Option for AToM
Ethernet VLAN
Examples
The following example shows a pseudowire class configuration that enables the L2VPN interworking:
Device(config)# pseudowire-class ip-interworking
Device(config-pw-class)# encapsulation mpls
Device(config-pw-class)# interworking ip
The following example shows an xconnect configuration that enables L2VPN interworking:
Device(config)# l2vpn xconnect context con1
Device(config-xconnect)# interworking ip
Related Commands
Command
Description
encapsulation l2tpv3
Specifies that L2TPv3 is used as the data encapsulation method for tunneling IP traffic over the pseudowire.
encapsulation mpls
Specifies that MPLS is used as the data encapsulation method for tunneling Layer 2 traffic over the pseudowire.
interval (MPLS-TP)
To configure the transmit and receive intervals between Bidirectional Forwarding Detection (BFD) packets and to specify the number of consecutive BFD control packets to miss before BFD declares that a peer is unavailable, use the intervalcommand in BFD configuration mode. To disable interval values, use the no form of this command.
(Optional) Specifies, in microseconds, the rate at which BFD control packets are sent to and received from BFD peers. If the microseconds keyword is not specified, the interval defaults to milliseconds.
bothtime
Specifies the rate at which BFD control packets are sent to BFD peers and the rate at which BFD control packets are received from BFD peers.
min-txtime
Specifies the rate at which BFD control packets are sent to BFD peers.
min-rxtime
Specifies, the rate at which BFD control packets are received from BFD peers.
multipliermultiplier-value
(Optional) Specifies the number of consecutive BFD control packets that must be missed from a BFD peer before BFD declares that the peer is unavailable and the Layer 3 BFD peer is informed of the failure. Range: 3 to 50. Default: 3.
Command Default
No session parameters are set.
Command Modes
BFD configuration (config-bfd)
Command History
Release
Modification
15.1(1)SA
This command was introduced.
15.1(3)S
This command was integrated.
Usage Guidelines
The interval command allows you to configure the session parameters for a BFD template.
Examples
The following example shows how to configure interval settings for the node1 BFD template:
Creates a BFD template and enters BFD configuration mode.
ip explicit-path
To enter the command mode for IP explicit paths and create or modify the specified path, use the
ip explicit-path command in global configuration mode. An IP explicit path is a list of IP addresses, each representing a node or link in the explicit path. To disable this feature, use the
no form of this command.
Number of the explicit path. The range is 1 to 65535.
enable
(Optional) Enables the path.
disable
(Optional) Prevents the path from being used for routing while it is being configured.
Command Modes
Global configuration (config)
Command History
Release
Modification
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T.
12.0(10)ST
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Cisco IOS XE Release 2.3
This command was integrated into Cisco IOS XE Release 2.3.
Examples
The following example shows how to enter the explicit path command mode for IP explicit paths and creates a path numbered 500:
Router(config)# ip explicit-path identifier 500
Router(config-ip-expl-path)#
Related Commands
Command
Description
append-after
Inserts the new path entry after the specified index number. Commands might be renumbered as a result.
index
Inserts or modifies a path entry at a specific index.
ip route vrf
Displays all or part of the explicit paths.
next-address
Specifies the next IP address in the explicit path.
show ip explicit-paths
Displays the configured IP explicit paths.
ip flow-cache mpls label-positions
To enable Multiprotocol Label Switching (MPLS)-Aware NetFlow, use the
ip flow-cache mpls label-positions command in global configuration mode. To disable MPLS-aware NetFlow, use the
no form of this command.
(Optional) Position of an MPLS label in the incoming label stack. Label positions are counted from the top of the stack, starting with 1.
exp-bgp-prefix-fields
(Optional) Generates a MPLS Provider Edge (PE) PE-to-PE traffic matrix.
The following IP-related flow fields are included:
Input interface
BGP Nexthop
MPLS Experimental (EXP) bits
The MPLS label values will be set to zero on the Cisco 10000 in the display output of the
show ip cache verbose flow aggregation exp-bgp-prefix command.
no-ip-fields
(Optional) Controls the capture and reporting of MPLS flow fields. If the
no-ip-fields keyword is not specified, the following IP-related flow fields are included:
Source IP address
Destination IP address
Transport layer protocol
Source application port number
Destination application port number
IP type of service (ToS)
TCP flag
If the
no-ip-fields keyword is specified, the IP-related fields are reported with a value of 0.
mpls-length
(Optional) Controls the reporting of packet length. If the
mpls-length keyword is specified, the reported length represents the sum of the MPLS packet payload length and the MPLS label stack length. If the
mpls-length keyword is not specified, only the length of the MPLS packet payload is reported.
Command Default
MPLS-Aware NetFlow is not enabled.
Command Modes
Global configuration (config)
Command History
Release
Modification
12.0(24)S
This command was introduced.
12.0(25)S
The
no-ip-fields and
mpls-length keywords were added.
12.3(8)T
This command was integrated into Cisco IOS Release 12.3(8)T.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31)SB2. The
exp-bgp-prefix-fields keyword was added.
Usage Guidelines
You must have NetFlow accounting configured on your router before you can use this command.
Use this command to configure the MPLS-aware NetFlow feature on a label switch router (LSR) and to specify labels of interest in the incoming label stack. Label positions are counted from the top of the stack, starting with 1. The position of the top label is 1, the position of the second label is 2, and so forth.
With MPLS-aware NetFlow enabled on the router, NetFlow collects data for incoming IP packets and for incoming MPLS packets on all interfaces where NetFlow is enabled in full or in sampled mode.
Caution
When you enter the
ip flow-cache mpls label-positions command on a Cisco 12000 series Internet router, NetFlow will stop collecting data for incoming IP packets on any Engine 4P line cards installed in the router on which NetFlow is enabled in full or in sampled mode. Engine 4P line cards in a Cisco 12000 series Internet router do not support NetFlow data collection of incoming IP packets and MPLS packets concurrently.
Tip
MPLS-aware NetFlow is enabled in global configuration mode. NetFlow is enabled per interface.
Examples
The following example shows how to configure MPLS-aware NetFlow to capture the first (top), third, and fifth label:
Router(config)# ip flow-cache mpls label-positions 1 3 5
The following example shows how to configure MPLS-aware NetFlow to capture only MPLS flow information (no IP-related flow fields) and the length that represents the sum of the MPLS packet payload length and the MPLS label stack length:
Router(config)# ip flow-cache mpls label-positions no-ip-fields mpls-length
The following example shows how to configure MPLS PE-to-PE Traffic Statistics for Netflow:
Router(config)# ip flow-cache mpls label-positions 1 2 exp-bgp-prefix-fields
Related Commands
Command
Description
ip flow-cache entries
Changes the number of entries maintained in the NetFlow accounting cache.
Enables NetFlow egress accounting for traffic that the router is forwarding.
ip flow-egress input-interface
Removes the NetFlow egress accounting flow key that specifies an output interface and adds a flow key that specifies an input interface for NetFlow egress accounting.
ip flow ingress
Enables NetFlow (ingress) accounting for traffic arriving on an interface.
show ip cache flow
Displays a summary of the NetFlow accounting statistics.
show ip cache verbose flow
Displays a detailed summary of the NetFlow accounting statistics.
show ip flow interface
Displays NetFlow accounting configuration for interfaces.
ip multicast mpls traffic-eng
To enable IP multicast traffic on a tailend router enabled with Multiprotocol Label Switching (MPLS) traffic engineering (TE) point-to-multipoint (P2MP) functionality, use the
ip multicast mpls traffic-eng command in privileged EXEC mode. To disable IP multicast for MPLS TE P2MP on tailend routers, use the
no form of this command.
ipmulticastmplstraffic-eng
[ range
{ access-list-number | access-list-name } ]
noipmulticastmplstraffic-eng [range]
Syntax Description
range
(Optional) Enables multicast for a specific set of multicast streams.
access-list-number
The specific number of the access list. Valid values are 100-199.
access-list-name
The specific name of the access list.
Command Default
MPLS TE P2MP functionality is not enabled.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.2(33)SRE
This command was introduced.
Usage Guidelines
You configure this command on the tailend routers in an MPLS TE P2MP topology.
Examples
The following example enables multicast routing on tailend routers configured with MPLS TE P2MP functionality:
Router(config)# ip multicast-routing
Router(config)# ip multicast mpls traffic-eng
Related Commands
Command
Description
show ip mroute
Displays IP multicast forwarding on MPLS TE P2MP tailend routers.
ip path-option
To specify an explicit or dynamic path option for a particular destination address in a destination list, use the
ip path-option command in traffic engineering destination list configuration mode. To remove the path option, use the
no form of this command.
The preference for this path option for the same destination address. The valid values are 1-1000. Only one path option is supported for each destination address.
dynamic
Specifies that the traffic engineering paths be dynamically computed.
explicit
Specifies that the traffic engineering paths be explicitly configured.
namename
Specifies the name of the explicit path.
identifiernumber
Specifies the number of the explicit path.
verbatim
(Optional) Specifies that the path should be sent out without any checking.
Command Default
Path options are not configured.
Command Modes
Traffic engineering destination list (cfg-te-dest-list)
Command History
Release
Modification
12.2(33)SRE
This command was introduced.
Usage Guidelines
The
ip path-option command is supported at a sublabel switched path (sub-LSP) level.
Point-to-multipoint traffic engineering supports only one path option per destination.
Examples
The following example shows the configuration of a destination list with explicit path options:
Router(config)# mpls traffic-eng destination list identifier 1
Router(cfg-te-dest-list)# ip 10.10.10.10 path-option 1 explicit identifier 1
Related Commands
Command
Description
mpls traffic-eng destination list
Specifies a MPLS traffic engineering point-to-multipoint destination list.
ip route static inter-vrf
To allow static routes to point to Virtual Private Network (VPN) routing and forwarding (VRF) interfaces other than those to which the static route belongs, use the
ip route static inter-vrf command in global configuration mode. To prevent static routes from pointing to VRF interfaces in VRFs to which they do not belong, use the
no form of this command.
iproutestaticinter-vrf
noiproutestaticinter-vrf
Syntax Description
This command has no arguments or keywords.
Command Default
Static routes are allowed to point to VRF interfaces in any VRF.
Command Modes
Global configuration
Command History
Release
Modification
12.0(23)S
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Usage Guidelines
The
ip route static inter-vrf command is turned on by default. The
no ip route static inter-vrf command causes the respective routing table (global or VRF) to reject the installation of static routes if the outgoing interface belongs to a different VRF than the static route being configured. This prevents security problems that can occur when static routes that point to a VRF interface in a different VRF are misconfigured. You are notified when a static route is rejected, then you can reconfigure it.
For example, a static route is defined on a provider edge (PE) router to forward Internet traffic to a customer on the interface pos1/0, as follows:
Router(config)# ip route 10.1.1.1 255.255.255.255 pos 1/0
The same route is mistakenly configured with the next hop as the VRF interface pos10/0:
Router(config)# ip route 10.1.1.1 255.255.255.255 pos 10/0
By default, Cisco IOS software accepts the command and starts forwarding the traffic to both pos1/0 (Internet) and pos10/0 (VPN) interfaces.
If the static route is already configured that points to a VRF other than the one to which the route belongs when you issue the
no ip route static inter-vrf command, the offending route is uninstalled from the routing table and a message similar to the following is sent to the console:
01:00:06: %IPRT-3-STATICROUTESACROSSVRF: Un-installing static route x.x.x.x/32
from global routing table with outgoing interface intx/x
If you enter the
no ip route static inter-vrf command before a static route is configured that points to a VRF interface in a different VRF, the static route is not installed in the routing table and a message is sent to the console.
Configuring the
no ip route static inter-vrf command prevents traffic from following an unwanted path. A VRF static route points to a global interface or any other VRF interface as shown in the following
ip route vrf commands:
Interface serial 1/0.0 is a global interface:
Router(config)# no ip route static inter-vrf
Router(config)# ip route vrf vpn1 10.10.1.1 255.255.255.255 serial 1/0.0
Interface serial 1/0.1 is in vpn2:
Router(config)# no ip route static inter-vrf
Router(config)# ip route vrf vpn1 10.10.1.1 255.255.255.255 serial 1/0.1
With the
no ip route static inter-vrf command configured, these static routes are not installed into the vpn1 routing table because the static routes point to an interface that is not in the same VRF.
If you require a VRF static route to point to a global interface, you can use the
global keyword with the
ip route vrf command:
Router(config)# ip route vrf vpn1 10.12.1.1 255.255.255.255 serial 1/0.0 10.0.0.1 global
The
global keyword allows the VRF static route to point to a global interface even when the
no ip route static inter-vrf command is configured.
Examples
The following example shows how to prevent static routes that point to VRF interfaces in a different VRF:
Router(config)# no ip route static inter-vrf
Related Commands
Command
Description
ip route vrf
Establishes static routes for a VRF.
ip route vrf
To establish static routes for a Virtual Private Network (VPN) routing and forwarding (VRF) instance, use the
ip route vrf command in global configuration mode. To disable static routes, use the
no form of this command.
IP route prefix for the destination, in dotted decimal format.
mask
Prefix mask for the destination, in dotted decimal format.
next-hop-address
(Optional) IP address of the next hop (the forwarding router that can be used to reach that network).
interface
(Optional) Name of network interface to use.
interface-number
(Optional) Number identifying the network interface to use.
global
(Optional) Specifies that the given next hop address is in the non-VRF routing table.
distance
(Optional) An administrative distance for this route.
permanent
(Optional) Specifies that this route will not be removed, even if the interface shuts down.
tagtag
(Optional) Specifies the label (tag) value that can be used for controlling redistribution of routes through route maps.
Command Default
No default behavior or values.
Command Modes
Global configuration
Command History
Release
Modification
12.0(5)T
This command was introduced.
12.0(21)ST
This command was integrated into Cisco IOS 12.0(21)ST.
12.0(22)S
This command was integrated into Cisco IOS 12.0(22)S.
12.2(13)T
This command was integrated into Cisco IOS 12.2(13)T.
12.2(14)S
This command was integrated into Cisco IOS 12.2(14)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
XE 2.5
This command was integrated into Cisco IOS XE Release 2.5.
Usage Guidelines
Use a static route when the Cisco IOS software cannot dynamically build a route to the destination.
If you specify an administrative distance when you set up a route, you are flagging a static route that can be overridden by dynamic information. For example, Interior Gateway Routing Protocol (IGRP)-derived routes have a default administrative distance of 100. To set a static route to be overridden by an IGRP dynamic route, specify an administrative distance greater than 100. Static routes each have a default administrative distance of 1.
Static routes that point to an interface are advertised through the Routing Information Protocol (RIP), IGRP, and other dynamic routing protocols, regardless of whether the routes are redistributed into those routing protocols. That is, static routes configured by specifying an interface lose their static nature when installed into the routing table.
However, if you define a static route to an interface not defined in a network command, no dynamic routing protocols advertise the route unless a
redistribute static command is specified for these protocols.
If a VPNv4 prefix in a given VRF is added to the global routing table, and there is recirculation on the corresponding VPN label due to egress features (ACL, Netflow, or QoS) configured on the outgoing interface, the traffic is not routed inside the VRF routing table, but inside the global routing table. If the same prefix exists in the global table, it results in a Layer 3 loop. To avoid this occurrence, use the
mls mpls recir-agg
command to switch off the VPN-CAM used for the VRF lookups, and to allocate the reserved VLAN for every VRF instance configured on the Cisco 7600 series routers.
Supported Static Route Configurations
When you configure static routes in a Multiprotocol Label Switching (MPLS) or MPLS VPN environment, note that some variations of the
ip route and
ip route vrf commands are not supported. These variations of the commands are not supported in Cisco IOS releases that support the Tag Forwarding Information Base (TFIB), specifically Cisco IOS releases 12.x T, 12.x M, and 12.0S. The TFIB cannot resolve prefixes when the recursive route over which the prefixes travel disappears and then reappears. However, the command variations are supported in Cisco IOS releases that support the MPLS Forwarding Infrastructure (MFI), specifically Cisco IOS release 12.2(25)S and later releases. Use the following guidelines when configuring static routes.
Supported Static Routes in an MPLS Environment
The following
ip route command is supported when you configure static routes in an MPLS environment:
ip routedestination-prefix mask interface next-hop-address
The following
ip route commands are supported when you configure static routes in an MPLS environment and configure load sharing with static nonrecursive routes and a specific outbound interface:
ip routedestination-prefix maskinterface1 next-hop1 ip routedestination-prefix maskinterface2 next-hop2
Unsupported Static Routes in an MPLS Environment That Uses the TFIB
The following
ip route command is not supported when you configure static routes in an MPLS environment:
ip routedestination-prefix mask next-hop-address
The following
ip route command is not supported when you configure static routes in an MPLS environment and enable load sharing where the next hop can be reached through two paths:
ip routedestination-prefix mask next-hop-address
The following
ip route command is not supported when you configure static routes in an MPLS environment and enable load sharing where the destination can be reached through two next hops:
ip routedestination-prefix masknext-hop1 ip routedestination-prefix masknext-hop2
Use the
interface and
next-hop arguments when specifying static routes.
Supported Static Routes in an MPLS VPN Environment
The following
ip route vrf commands are supported when you configure static routes in an MPLS VPN environment, and the next hop and interface are in the same VRF:
The following
ip route vrf commands are supported when you configure static routes in an MPLS VPN environment, and the next hop is in the global table in the MPLS cloud in the global routing table. For example, these commands are supported when the next hop is pointing to the Internet gateway.
iproutevrfvrf-namedestination-prefixmaskinterfacenext-hop-address (This command is supported when the next hop and interface are in the core.)
The following
ip route commands are supported when you configure static routes in an MPLS VPN environment and enable load sharing with static nonrecursive routes and a specific outbound interface:
Unsupported Static Routes in an MPLS VPN Environment That Uses the TFIB
The following
ip route command is not supported when you configure static routes in an MPLS VPN environment, the next hop is in the global table in the MPLS cloud within the core, and you enable load sharing where the next hop can be reached through two paths:
The following
ip route commands are not supported when you configure static routes in an MPLS VPN environment, the next hop is in the global table in the MPLS cloud within the core, and you enable load sharing where the destination can be reached through two next hops:
The following
ip route vrf commands are not supported when you configure static routes in an MPLS VPN environment, and the next hop and interface are in the same VRF:
Supported Static Routes in an MPLS VPN Environment Where the Next Hop Resides in the Global Table on the CE Router
The following
ip route vrf command is supported when you configure static routes in an MPLS VPN environment, and the next hop is in the global table on the customer equipment (CE) side. For example, the following command is supported when the destination prefix is the CE router’s loopback address, as in external BGP (EBGP) multihop cases.
The following
ip route commands are supported when you configure static routes in an MPLS VPN environment, the next hop is in the global table on the CE side, and you enable load sharing with static nonrecursive routes and a specific outbound interfaces:
The following command shows how to reroute packets addressed to network 10.23.0.0 in VRF vpn3 to router 10.31.6.6:
Router(config)# ip route vrf vpn3 10.23.0.0 255.255.0.0 10.31.6.6
Related Commands
Command
Description
show ip route vrf
Displays the IP routing table associated with a VRF.
redistribute static
Redistributes routes from another routing domain into the specified domain.
ip rsvp msg-pacing
Note
Effective with Cisco IOS Release 12.2(13)T, the
ip rsvp msg-pacing command is replaced by the
ip rsvp signalling rate-limit command. See the
ip rsvp signalling rate-limit command for more information.
To configure the transmission rate for Resource Reservation Protocol (RSVP) messages, use the
ip rsvp msg-pacing command in global configuration mode. To disable this feature, use the
no form of this command.
(Optional) Length of the interval, in milliseconds, during which a router can send the number of RSVP messages specified in the
burst keyword. The value can be from 1 to 1000 milliseconds.
burstmsgs
(Optional) Maximum number of RSVP messages that a router can send to an output interface during each interval specified in the
period keyword. The value can be from 1 to 2000.
maxsizeqsize
(Optional) Size of per-interface output queues in the sending router. Valid values are from 1 to 2000.
Command Default
RSVP messages are not paced. If you enter the command without the optional
burst keyword, the transmission rate for RSVP messages is limited to 200 messages per second per outgoing interface. The default output queue size, specified in the
maxsize keyword, is 500.
Command Modes
Global configuration (config)
Command History
Release
Modification
12.0(14)ST
This command was introduced.
12.2(11)S
This command was integrated into Cisco IOS Release 12.2(11)S.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
12.2(13)T
This command was replaced with the
ip rsvp signalling rate-limit command.
Usage Guidelines
You can use this command to prevent a burst of RSVP traffic engineering signaling messages from overflowing the input queue of a receiving router. Overflowing the input queue with signaling messages results in the router dropping some messages. Dropped messages substantially delay the completion of signaling for LSPs for which messages have been dropped.
If you enter the
ip rsvp msg-pacing command without the optional
burst keyword, the transmission rate for RSVP messages is limited to 200 messages per second per outgoing interface. The default output queue size, specified in the
maxsize keyword, is 500.
Examples
The following example shows how to configure a router to send a maximum of 150 RSVP traffic engineering signaling messages in 1 second to a neighbor, and the size of the output queue is 750:
Router(config)# ip rsvp msg-pacing period 1 burst 150 maxsize 750
Related Commands
Command
Description
clear ip rsvp msg-pacing
Clears the RSVP message pacing output from the
show ip rsvp neighbor command.
ip rsvp signalling hello (configuration)
To enable Hello globally on the router, use the iprsvpsignallinghellocommand in global configuration mode. To disable Hello globally on the router, use the no form of this command.
iprsvpsignallinghello
noiprsvpsignallinghello
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Global configuration
Command History
Release
Modification
12.0(22)S
This command was introduced.
12.2(18)SXD1
This command was integrated into Cisco IOS Release 12.2(18)SXD1.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31)SB2.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines
To enable Hello globally on the router, you must enter this command. You also must enable Hello on the interface.
Examples
In the following example, Hello is enabled globally on the router:
Router(config)# ip rsvp signalling hello
Related Commands
Command
Description
iprsvpsignallinghello(interface)
Enables Hello on an interface where you need Fast Reroute protection.
iprsvpsignallinghellostatistics
Enables Hello statistics on the router.
ip rsvp signalling hello (interface)
To enable hello on an interface where you need Fast Reroute protection, use the iprsvpsignallinghellocommand in interface configuration mode. To disable hello on an interface where you need Fast Reroute protection, use the no form of this command
iprsvpsignallinghello
noiprsvpsignallinghello
Syntax Description
This command has no arguments or keywords.
Command Default
No hellos are enabled.
Command Modes
Interface configuration (config-if)
Command History
Release
Modification
12.0(22)S
This command was introduced.
12.2(18)SXD1
This command was integrated into Cisco IOS Release 12.2(18)SXD1.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31)SB2.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines
You must configure hello globally on a router and on the specific interface.
Examples
In the following example, hello is enabled on an interface:
Router(config-if)# ip rsvp signalling hello
Related Commands
Command
Description
iprsvpsignallinghello(configuration)
Enables Hello globally on the router.
iprsvpsignallinghellodscp
Sets the DSCP value that is in the IP header of the Hello messages sent out from the interface.
iprsvpsignallinghellorefreshmisses
Specifies how many Hello acknowledgments a node can miss in a row before the node considers that communication with its neighbor is down.
iprsvpsignallinghellorefreshinterval
Configures the Hello request interval.
ip rsvp signalling hello bfd (configuration)
To enable the Bidirectional Forwarding Detection (BFD) protocol globally on the router for Multiprotocol Label Switching (MPLS) traffic engineering (TE) link and node protection, use the
ip rsvp signalling hello bfd command in global configuration mode. To disable BFD globally on the router, use the
no form of this command.
iprsvpsignallinghellobfd
noiprsvpsignallinghellobfd
Syntax Description
This command has no arguments or keywords.
Command Default
BFD is not enabled globally on the router for MPLS TE link and node protection.
Command Modes
Global configuration
Command History
Release
Modification
12.2(33)SRC
This command was introduced.
15.1(1)SY
This command was integrated into Cisco IOS Release 15.1(1)SY.
Usage Guidelines
To enable the BFD protocol on the router, you must enter this command. You also must enter the
ip rsvp signalling hello bfd command on the interface.
Examples
The following example allows you to use the BFD protocol on the router for MPLS TE link and node protection:
Router(config)# ip rsvp signalling hello bfd
Related Commands
Command
Description
ip rsvp signalling hello bfd (interface)
Enables the BFD protocol on an interface where you need MPLS TE link and node protection.
show ip rsvp hello bfd nbr
Displays information about all MPLS TE clients that use the BFD protocol.
show ip rsvp hello bfd nbr detail
Displays detailed information about all MPLS TE clients that use the BFD protocol.
show ip rsvp hello bfd nbr summary
Displays summarized information about all MPLS TE clients that use the BFD protocol.
ip rsvp signalling hello bfd (interface)
To enable the Bidirectional Forwarding Detection (BFD) protocol on an interface for Multiprotocol Label Switching (MPLS) traffic engineering (TE) link and node protection, use the
ip rsvp signalling hello bfd command in interface configuration mode. To disable BFD on an interface for MPLS TE link and node protection, use the
no form of this command.
iprsvpsignallinghellobfd
noiprsvpsignallinghellobfd
Syntax Description
This command has no arguments or keywords.
Command Default
BFD is not enabled on an interface.
Command Modes
Interface configuration
Command History
Release
Modification
12.2(33)SRC
This command was introduced.
15.1(1)SY
This command was integrated into Cisco IOS Release 15.1(1)SY.
15.2(2)SNG
This command was integrated into Cisco ASR 901 Series Aggregation Services Routers.
15.3(1)S
This command was integrated into Cisco IOS Release 15.3(1)S.
Usage Guidelines
You must enter the
ip rsvp signalling hello bfd command on the router and on the specific interface.
Examples
In the following example, the BFD protocol is enabled on an interface:
Router(config-if)# ip rsvp signalling hello bfd
Related Commands
Command
Description
ip rsvp signalling hello bfd (configuration)
Enables the BFD protocol on the router for MPLS TE link and node protection.
show ip rsvp hello bfd nbr
Displays information about all MPLS TE clients that use the BFD protocol.
show ip rsvp hello bfd nbr detail
Displays detailed information about all MPLS TE clients that use the BFD protocol.
show ip rsvp hello bfd nbr summary
Displays summarized information about all MPLS TE clients that use the BFD protocol.
ip rsvp signalling hello dscp
To set the differentiated services code point (DSCP) value that is in the IP header of a Resource Reservation Protocol (RSVP) traffic engineering (TE) hello message sent from an interface, use the iprsvpsignallinghellodscp command in interface configuration mode. To set the DSCP value to its default, use the no form of this command.
iprsvpsignallinghello [fast-reroute] dscpnum
noiprsvpsignallinghello [fast-reroute] dscp
Syntax Description
fast-reroute
(Optional) Initiates Fast Reroute capability.
num
DSCP value. Valid values are from 0 to 63.
Command Default
The default DSCP value is 48.
Command Modes
Interface configuration
Command History
Release
Modification
12.0(22)S
This command was introduced.
12.0(29)S
The optional fast-reroute keyword was added.
12.2(18)SXD1
This command was integrated into Cisco IOS Release 12.2(18)SXD1.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31)SB2.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines
If a link is congested, it is recommended that you set the DSCP to a value higher than 0 to reduce the likelihood that hello messages will be dropped.
You configure the DSCP per interface, not per flow.
The DSCP applies to the RSVP hellos created on a specific interface. You can configure each interface independently for DSCP.
If you issue the iprsvpsignallinghellodscp command without the optional fast-reroutekeyword, the command applies to Fast Reroute hellos. This command is provided for backward compatibility; however, we recommend that you use the iprsvpsignallinghellofast-reroutedscpcommand.
Examples
In the following example, hello messages sent from this interface have a DSCP value of 30 and Fast Reroute capability is enabled by specifying the fast-reroute keyword:
Router(config-if)# ip rsvp signalling hello fast-reroute dscp 30
In the following example, hello messages sent from this interface have a DSCP value of 30 and Fast Reroute capability is enabled by default:
Router(config-if)# ip rsvp signalling hello dscp 30
Related Commands
Command
Description
iprsvpsignallinghello(interface)
Enables hellos on an interface where you need Fast Reroute protection.
iprsvpsignallinghellorefreshinterval
Sets the hello refresh interval in hello messages.
iprsvpsignallinghellorerouterefreshmisses
Sets the missed refresh limit in hello messages.
ip rsvp signalling hello refresh interval
To configure the Resource Reservation Protocol (RSVP) traffic engineering (TE) hello refresh interval, use the iprsvpsignallinghellorefreshinterval command in interface configuration mode. To set the refresh interval to its default value, use theno form of this command.
Frequency, in milliseconds (msec), at which a node sends hello messages to a neighbor. Valid values are from 10 to 30000 msec.
Note
Values below the default of 200 msec are not recommended, because they can cause RSVP Hellos to falsely detect a neighbor down event and unecessarily trigger Fast ReRoute.
Command Default
The default frequencyat which a node sends hello messages to a neighbor is 200 msec.
Command Modes
Interface configuration
Command History
Release
Modification
12.0(22)S
This command was introduced.
12.0(29)S
The optional fast-reroutekeyword was added.
12.2(18)SXD1
This command was integrated into Cisco IOS Release 12.2(18)SXD1.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31)SB2.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines
You can configure the hello request interval on a per-interface basis. A node periodically generates a hello message containing a Hello Request object for each neighbor whose status is being tracked. The frequency of those hello messages is determined by the hello interval.
If you issue the iprsvpsignallinghellorefreshintervalcommand without the optional fast-reroutekeyword, the command applies to Fast Reroute hellos. This command is provided for backward compatibility; however, we recommend that you use the iprsvpsignallinghellofast-rerouterefreshintervalcommand.
Examples
In the following example, hello requests are sent to a neighbor every 5000 milliseconds and Fast Reroute capability is enabled by specifying the fast-reroute keyword:
Router(config-if)# ip rsvp signalling hello fast-reroute refresh interval 5000
In the following example, hello requests are sent to a neighbor every 5000 milliseconds and Fast Reroute capability is enabled by default:
Router(config-if)# ip rsvp signalling hello refresh interval 5000
Sets the refresh interval in graceful restart hello messages.
iprsvpsignallinghellorerouterefreshmisses
Sets the missed refresh limit in hello messages.
ip rsvp signalling hello refresh misses
To specify how many Resource Reservation Protocol (RSVP) traffic engineering (TE) hello acknowledgments a node can miss in a row before the node considers that communication with its neighbor is down, use the iprsvpsignallinghellorefreshmisses command in interface configuration mode. To return the missed refresh limit to its default value, use the no form of this command.
Number of sequential hello acknowledgments that a node can miss before RSVP considers the state expired and tears it down. Valid values are from 4 to 10.
Command Default
The default number of sequential hello acknowledgments is 4.
Command Modes
Interface configuration
Command History
Release
Modification
12.0(22)S
This command was introduced.
12.0(29)S
The optional fast-reroute keyword was added.
12.2(18)SXD1
This command was integrated into Cisco IOS Release 12.2(18)SXD1.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31)SB2.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T
Usage Guidelines
A hello comprises a hello message, a Hello Request object, and a Hello ACK object. Each request is answered by an acknowledgment. If a link is very congested or a router has a very heavy load, set this number to a value higher than the default value to ensure that hello does not falsely declare that a neighbor is down.
If you issue the iprsvpsignallinghellorefreshmissescommand without the optional fast-reroutekeyword, the command applies to Fast Reroute hellos and Fast Reroute capability is enabled by default. This command is provided for backward compatibility; however, we recommend that you use the iprsvpsignallinghellofast-rerouterefreshmissescommand.
Examples
In the following example, if the node does not receive five hello acknowledgments in a row, the node declares that its neighbor is down and Fast Reroute is enabled by specifying the fast-reroute keyword:
Router(config-if)# ip rsvp signalling hello fast-reroute refresh misses 5
In the following example, if the node does not receive five hello acknowledgments in a row, the node declares that its neighbor is down and Fast Reroute is enabled by default:
Router(config-if)# ip rsvp signalling hello refresh misses 5
Related Commands
Command
Description
iprsvpsignallinghellodscp
Sets the DSCP value in hello messages.
iprsvpsignallinghellorefreshinterval
Sets the refresh interval in hello messages.
ip rsvp signalling hello statistics
To enable Hello statistics on the router, use the iprsvpsignallinghellostatistics command in global configuration mode. To disable Hello statistics on the router, use the no form of this command.
iprsvpsignallinghellostatistics
noiprsvpsignallinghellostatistics
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Global configuration
Command History
Release
Modification
12.0(22)S
This command was introduced.
12.2(18)SXD1
This command was integrated into Cisco IOS Release 12.2(18)SXD1.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31)SB2.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
Examples
In the following example, Hello statistics are enabled on the router:
Router(config)# ip rsvp signalling hello statistics
Related Commands
Command
Description
cleariprsvphelloinstancestatistics
Clears Hello statistics for an instance.
iprsvpsignallinghello(configuration)
Enables Hello globally on the router.
showiprsvphellostatistics
Displays how long Hello packets have been in the Hello input queue.
ip vrf
To define a VPN
routing and forwarding (VRF) instance and to enter VRF configuration mode, use
the
ipvrf command in global configuration mode. To
remove a VRF instance, use the
no form of this
command.
ipvrfvrf-name
noipvrfvrf-name
Syntax Description
vrf-name
Name
assigned to a VRF.
Command Default
No VRFs are
defined. No import or export lists are associated with a VRF. No route maps are
associated with a VRF.
Command Modes
Global
configuration (config)
Command History
Release
Modification
12.0(5)T
This
command was introduced.
12.0(21)ST
This
command was integrated into Cisco IOS Release 12.0(21)ST.
12.0(22)S
This
command was integrated into Cisco IOS Release 12.0(22)S.
12.2(14)S
This
command was integrated into Cisco IOS 12.2(14)S.
12.2(28)SB
This
command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This
command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH
This
command was integrated into Cisco IOS Release 12.2(33)SXH.
Cisco IOS
XE Release 2.1
This
command was integrated into Cisco IOS XE Release 2.1.
15.1(1)SY
This
command was integrated into Cisco IOS Release 15.1(1)SY.
Cisco IOS XE 3.3SE
This command was implemented in Cisco IOS XE Release 3.3SE.
Usage Guidelines
The
ipvrfvrf-name
command creates a VRF instance named
vrf-name. To
make the VRF functional, a route distinguisher (RD) must be created using the
rdroute-distinguisher command in VRF configuration
mode. The
rdroute-distinguisher command creates the routing
and forwarding tables and associates the RD with the VRF instance named
vrf-name.
The
ipvrfdefault command can be used to configure a VRF
instance that is a NULL value until a default VRF name can be configured. This
is typically before any VRF related AAA commands are configured.
Examples
The following
example shows how to import a route map to a VRF instance named VPN1:
Router(config)# ip vrf vpn1
Router(config-vrf)# rd 100:2
Router(config-vrf)# route-target both 100:2
Router(config-vrf)# route-target import 100:1
Related Commands
Command
Description
ipvrfforwarding(interfaceconfiguration)
Associates a VRF with an interface or subinterface.
rd
Creates
routing and forwarding tables for a VRF and specifies the default route
distinguisher for a VPN.
ip vrf forwarding (interface configuration)
To associate a Virtual Private Network (VPN) routing and forwarding (VRF) instance with an interface or subinterface, use the
ip vrf forwarding command in interface configuration mode. To disassociate a VRF, use the
no form of this command.
ipvrfforwardingvrf-name
[ downstreamvrf-name2 ]
noipvrfforwardingvrf-name
[ downstreamvrf-name2 ]
Syntax Description
vrf-name
Associates the interface with the specified VRF.
downstream
(Optional) Enables Half Duplex VRF (HDVRF) functionality on the interface and associates the interface with the downstream VRF.
vrf-name2
(Optional) Associates the interface with the specified downstream VRF.
Command Default
The default for an interface is the global routing table.
Command Modes
Interface configuration
Command History
Release
Modification
12.0(5)T
This command was introduced.
12.3(6)
The downstream keyword was added to support MPLS VPN Half-Duplex VRFs.
12.3(11)T
This command was modified. Support was added for interfaces and subinterfaces that are configured with X.25 encapsulation.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Cisco IOS XE Release 2.5
This command was modified. This command was implemented on the Cisco ASR 1000 Series Aggregation Services Routers.
15.1(2)SNG
This command was integrated into Cisco ASR 901 Series Aggregation Services Routers.
Usage Guidelines
Use this command to associate an interface with a VRF. Executing this command on an interface removes the IP address. The IP address should be reconfigured. The
downstream keyword is available on supported platforms with virtual interfaces. The
downstream keyword associates the interfaces with a downstream VRF, which enables half duplex VRF functionality on the interface. Some functions operate in the upstream VRFs, and others operate in the downstream VRFs. The following functions operate in the downstream VRFs:
PPP peer routes are installed in the downstream VRFs.
Authentication, authorization, and accounting (AAA) per-user routes are installed in the downstream VRFs.
A Reverse Path Forwarding (RPF) check is performed in the downstream VRFs.
Forwarding Between X.25 Interfaces and Interfaces Configured for MPLS
This command enables IP forwarding between X.25 interfaces and interfaces configured for MPLS, which lets you connect customer premises equipment (CPE) devices to a provider edge (PE) router via an X.25 network by forwarding IP traffic between the CPE devices and the MPLS network. You must configure MPLS on the PE and provider routers in the network.
This command lets you perform an X.25 aggregation function on a PE router for several CPE devices with X.25 VCs into an MPLS network. The PE router performs the aggregation function of terminating X25 VCs and also performs the mapping function (in which VCs are mapped to the appropriate MPLS VRF domains).
Distributed CEF switching, CEF switching, and fast switching are not supported (only process switching is supported). Forwarding of IPv6 traffic is not supported.
Note
Configuring IP VRF forwarding on an interface or subinterface that already has an IP address causes that IP address to be deleted from the running configuration. On an X.25 interface or subinterface, it does not cause any existing
x25 map ip or
x25 pvc ip statements to be deleted. Configuring an
x25 map ip or
x25 pvc ip statement with an IP address that matches an IP address configured on the same interface (or any subinterface of the same interface) might be rejected, even when the conflicting address is in another VRF instance.
For additional references, see CCITT 1988 Recommendation X.25 (Interface Between Data Terminal Equipment (DTE) and Data Circuit-Terminating Equipment (DCE) for Terminals Operating in the Packet Mode and Connected to Public Data Networks by Dedicated Circuit) , RFC 1356
(Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode) , and RFC 1461
(SNMP MIB extension for Multiprotocol Interconnect over X.25) .
Examples
The following example shows how to link a VRF to ATM interface 0/0:
Router(config)# interface atm0/0
Router(config-if)# ip vrf forwarding vpn1
The following example associates the VRF named U with the virtual-template 1 interface and specifies the downstream VRF named D:
Router> enable
Router# configure terminal
Router(config)# interface virtual-template 1
Router(config-if)# ip vrf forwarding U downstream D
Router(config-if)# ip unnumbered Loopback1
Related Commands
Command
Description
ip route vrf
Establishes static routes for a VRF.
ip vrf
Configures a VRF routing table.
show ip vrf
Displays the set of defined VRF instances and associated interfaces.
ip vrf receive
To insert the IP address of an interface as a connected route entry in a Virtual Private Network (VPN) routing and forwarding instance (VRF) routing table, use the
ip vrf receive command in interface configuration mode. To remove the connected entry from the VRF routing table, use the
no form of this command.
ipvrfreceivevrf-name
noipvrfreceivevrf-name
Syntax Description
vrf-name
Name assigned to a VRF into which you want to add the IP address of the interface.
Command Default
No IP address of an interface is inserted as connected route entry in a VRF routing table.
Command Modes
Interface configuration
Command History
Release
Modification
12.0(22)S
This command was introduced.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S
12.2(27)SBC
This command was integrated into Cisco IOS Release 12.2(27)SBC.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Usage Guidelines
The ip vrf receive command supports VRF route selection for the following features:
MPLS VPN: VRF Selection Based on Source IP Address
MPLS VPN: VRF Selection Using Policy-Based Routing
This command is used to install a primary or secondary IP address of an interface as a connected route entry in the VRF routing table. These entries appear as “receive” entries in the Cisco Express Forwarding table. MPLS VPNs require Cisco Express Forwarding switching to make IP destination prefix-based switching decisions. This command can be used to selectively install the interface IP address in the VRF that is specified with the vrf-name argument. Only the local interface IP address is added to the VRF routing table. This command is used on a per-VRF basis. In other words, you must enter this command for each VRF in which you need to insert the IP address of the interface. This command does not remove the interface IP address from the global routing table.
Note
This command cannot be used with the ip vrf forward command for the same interface.
VRF Selection Based on Source IP Address Guidelines
The
ip vrf receive command is automatically disabled when the
no ip vrfvrf-name command is entered for the local interface. An error message is displayed when the
ip vrf receive command is disabled in this manner. Interfaces where the VRF Selection Based on Source IP Address feature is enabled can forward packets that have an IP address that corresponds to an IP address entry in the VRF table. If the VRF table does not contain a matching IP address, the packet is dropped, by default, because there is no corresponding “receive” entry in the VRF entry.
VRF Selection Using Policy Based Routing Guidelines
You must enter the
ip policy route-map command before the
ip vrf receive command can be enabled. The ip vrf receive command is automatically disabled when either the
no ip policy route-mapmap-name or the
no ip vrfvrf-name command is entered for the local interface. An error message is displayed when the ip vrf receive command is disabled in this manner. With the VRF Selection Using Policy-Based Routing implementation of the VRF selection feature, a route map filters the VRF routes. If a match and set operation occurs in the route map but there is no receive entry in the local VRF table, the packet is dropped.
Examples
Examples
The following example shows how to configure Ethernet interface 0/2 (172.16.1.3) and insert its IP address in VRF1 and VRF2 with the ip vrf receive command. You must enter the ip vrf select source command on the interface or subinterface to enable VRF selection on the interface or subinterface. You must also enter the vrf selection source command in global configuration mode to populate the VRF selection table and to configure the VRF Selection Based on Source IP Address feature. (The vrf selection source command is not shown in this example.)
Router(config)# interface Ethernet0/2
Router(config-if)# ip address 172.16.1.3 255.255.255.255
Router(config-if)# ip vrf select source
Router(config-if)# ip vrf receive VRF1
Router(config-if)# ip vrf receive VRF2
Router(config-if)# end
Examples
The following example shows how to configure Ethernet interface 0/1 (192.168.1.2) and insert its IP address in VRF1 and VRF2 with the ip vrf receive command. You must configure an access list and a route map to allow the VRF Section Using Policy-Based Routing feature to select a VRF. (The access list and route map configuration are not shown in this example.)
Router(config)# interface Ethernet0/1
Router(config-if)# ip address 192.168.1.2 255.255.255.255
Router(config-if)# ip policy route-map PBR-VRF-SELECTION
Router(config-if)# ip vrf receive VRF1
Router(config-if)# ip vrf receive VRF2
Router(config-if)# end
Related Commands
Command
Description
access-list (IP standard)
Defines a standard IP access list.
ip vrf
Configures a VRF routing table.
ip vrf select source
Enables VRF selection on an interface.
set vrf
Enables VRF selection and filtering under a route map.
vrf selection source
Populates a single source IP address, or range of source IP addresses, to a VRF selection table.
ip vrf select source
To enable the VRF Selection feature on a particular interface or subinterface, use the
ip vrf select source command in interface configuration mode. To disable the VRF Selection feature on a particular interface or subinterface, use the
no form of this command.
ipvrfselectsource
noipvrfselectsource
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Interface configuration
Command History
Release
Modification
12.0(22)S
This command was introduced.
12.0(23)S
This command was integrated into Cisco IOS Release 12.0(23)S.
12.0(24)S
This command was integrated into Cisco IOS Release 12.0(24)S.
12.2(14)SZ
This command was integrated into Cisco IOS Release 12.2(14)SZ to support the Cisco 7304 router.
12.2(18)S
This command was integrated into Cisco IOS Release 12.2(18)S to support the Cisco 7304 router.
12.0(26)S
This command was integrated into Cisco IOS Release 12.0(26)S to support the Cisco 7200 and 7500 series routers.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S to support the Cisco 7200 and 7500 series routers.
12.2(27)SBC
This command was integrated into Cisco IOS Release 12.2(27)SBC.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Usage Guidelines
The
ip vrf select source and the
ip vrf forwarding commands are mutually exclusive. If the VRF Selection feature is configured on an interface, you cannot configure VRFs (using the
ip vrf forwarding command) on the same interface.
Examples
The following example shows how to enable the VRF Selection feature on an interface:
Router(config-if)# ip vrf select source
The following example shows the message you receive after you have deleted the VRF Selection feature on an interface:
Enter configuration commands, one per line. End with CNTL/Z.
Router (config)# interface pos4/0
Router (config-if)# no ip vrf select source
Router (config-if)#
INTERFACE_VRF_SELECT unset for POS4/0, slot: 4
Router (config-if)#
The following example shows the message you receive after you have enabled the VRF Selection feature on an interface:
Router (config-if)# ip vrf select source
Router (config-if)#
INTERFACE_VRF_SELECT set for POS4/0, slot: 4
Router (config-if)#
Related Commands
Command
Description
ip vrf receive
Adds all the IP addresses that are associated with an interface into a VRF table.
vrf selection source
Populates a single source IP address, or range of source IP addresses, to a VRF Selection table.
ip vrf sitemap
To configure Site of Origin (SoO) filtering on an interface, use the
ip vrf sitemap command in interface configuration mode. To disable SoO filtering on an interface, use the
no form of this command.
ipvrfsitemaproute-map
noipvrfsitemap
Syntax Description
route-map
The name of the route map that is configured with the as-number and network of the VPN site.
Command Default
No default behavior or values
Command Modes
Interface configuration
Command History
Release
Modification
12.2(13)T
This command was introduced.
12.0(24)S
This command was integrated into Cisco IOS Release 12.0(24)S.
12.2(18)SXE
This command was integrated into Cisco IOS Release 12.2(18)SXE.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
The SoO extended community is a BGP extended community attribute that is used to identify routes that have originated from a site so that the re-advertisement of that prefix back to the source site can be prevented. The SoO extended community attribute uniquely identifies the site from which a PE router has learned a route.
Examples
The following example configures SoO filtering on an interface:
Router(config)# route-map Site-of-Origin permit 10
Router(config-route-map)# set extcommunity soo 100:1
Router(config-route-map)# exit
Router(config)# interface FastEthernet 0/0
Router(config-if)# ip vrf forwarding RED
Router(config-if)# ip vrf sitemap Site-of-Origin
Router(config-if)# ip address 10.0.0.1 255.255.255.255
Router(config-if)# end
Related Commands
Command
Description
ip vrf forwarding
Associates a VRF with an interface or subinterface.
l2 pseudowire routing
To enter Layer 2 pseudowire routing configuration mode, use the
l2 pseudowire routing command in global configuration mode. To exit Layer 2 pseudowire routing configuration mode, use the
no form of this command.
l2pseudowirerouting
nol2pseudowirerouting
Syntax Description
This command has no arguments or keywords.
Command Default
Layer 2 pseudowire routing mode is not entered.
Command Modes
Global configuration (config)
Command History
Release
Modification
15.1(1)S
This command was introduced.
Cisco IOS XE Release 3.8S
This command was integrated into Cisco IOS XE Release 3.8S.
Usage Guidelines
The
l2 pseudowire routing command enters Layer 2 pseudowire routing configuration mode (config-l2_pw_rtg) from which you can use additional commands such as the
switching-point command and the
terminating-pe tie-breaker command. The
switching-point command and theterminating-pe tie-breaker command are used to configure the L2VPN VPLS Inter-AS Option B feature. For more information about the L2VPN VPLS Inter-AS Option B feature, see the
Multiprotocol Label Switching Configuration Guide .
Examples
The following example enables Layer 2 pseudowire routing configuration mode:
Configures a switching point and specifies a VC ID range.
terminating-pe tie-breaker
Negotiates the behavior mode (either active or passive) for a TPE router.
l2 vfi autodiscovery
To enable the Virtual Private LAN Service (VPLS) provider edge (PE) router to automatically discover other PE routers that are part of the same VPLS domain, use the
l2vfiautodiscovery command in global configuration mode. To disable VPLS autodiscovery, use the
no form of this command.
l2vfivfi-nameautodiscovery
nol2vfivfi-nameautodiscovery
Syntax Description
vfi-name
Specifies the name of the virtual forwarding instance. The virtual forwarding instance (VFI) identifies a group of pseudowires that are associated with a virtual switching instance (VSI).
Command Default
Layer 2 VFI autodiscovery is not enabled.
Command Modes
Global configuration (config)
Command History
Release
Modification
12.2(33)SRB
This command was introduced.
Cisco IOS XE Release 3.7S
This command was integrated into Cisco IOS XE Release 3.7S.
15.1(1)SY
This command was integrated into Cisco IOS Release 15.1(1)SY.
Usage Guidelines
VPLS Autodiscovery enables each VPLS PE router to discover other PE routers that are part of the same VPLS domain. VPLS Autodiscovery also automatically detects when PE routers are added to or removed from the VPLS domain. Beginning with Cisco IOS Release 12.2(33)SRB, you no longer need to manually configure the VPLS neighbors and maintain the configuration when a PE router is added or deleted. However, you can still perform manual VPLS configuration even when you enable VPLS Autodiscovery.
Examples
The following example enables VPLS Autodiscovery on a PE router:
l2 vfi vfi2 autodiscovery
Related Commands
Command
Description
l2vfimanual
Manually creates a Layer 2 VFI.
l2 vfi manual
To create a Layer 2 virtual forwarding instance (VFI) and enter Layer 2 VFI manual configuration mode, use the
l2vfimanual command in global configuration mode. To remove the Layer 2 VFI, use the
no form of this command.
l2vfinamemanual
nol2vfinamemanual
Syntax Description
name
Name of a new or existing Layer 2 VFI .
Command Default
The Layer 2 VFI is not configured.
Command Modes
Global configuration (config)
Command History
Release
Modification
12.2(18)SXF
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.
15.0(1)M
This command was integrated into a release earlier than Cisco IOS Release 15.0(1)M.
Cisco IOS XE Release 3.7S
This command was integrated into Cisco IOS XE Release 3.7S.
Usage Guidelines
A VFI is a collection of data structures used by the data plane, software-based or hardware-based, to forward packets to one or more virtual circuits (VC). It is populated and updated by both the control plane and the data plane and also serves as the data structure interface between the control plane and the data plane.
Within the Layer 2 VFI manual configuration mode, you can configure the following parameters:
VPN ID of a Virtual private LAN service (VPLS) domain
Addresses of other PE routers in this domain
Type of tunnel signaling and encapsulation mechanism for each peer
Within the Layer 2 VFI manual configuration mode, the following commands are available:
This example shows how to create a Layer 2 VFI, enter Layer 2 VFI manual configuration mode, and configure a VPN ID:
Router(config)# l2 vfi vfitest1 manual
Router(config-vfi)# vpn id 303
Related Commands
Command
Description
l2vfipoint-to-point
Establishes a point-to-point Layer 2 VFI between two separate networks.
vpnid
Configures a VPN ID in RFC 2685 format. You can change the value of the VPN ID only after its configuration, and you cannot remove it.
neighbor
Specifies the type of tunnel signaling and encapsulation mechanism for each peer.
l2 vfi point-to-point
To establish a point-to-point Layer 2 virtual forwarding interface (VFI) between two separate networks, use the
l2 vfi point-to-point command in global configuration mode. To disable the connection, use the
no form of this command.
l2vfinamepoint-to-point
nol2vfinamepoint-to-point
Syntax Description
name
Name of the connection between the two networks.
Command Default
Point-to-point Layer 2 virtual forwarding interfaces are not created.
Command Modes
Global configuration (config)
Command History
Release
Modification
12.0(31)S
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
15.0(1)M
This command was integrated into a release earlier than Cisco IOS Release 15.0(1)M.
Usage Guidelines
If you disable L2VPN Pseudowire Switching with the
no l2 vfi point-to-point command, the virtual circuits (VCs) are deleted.
Examples
The following example establishes a point-to-point Layer 2 VFI:
Router(config)# l2 vfi atomvfi point-to-point
Related Commands
Command
Description
neighbor (L2VPN Pseudowire Switching)
Establishes the two routers with which to form a connection.
l2vpn
To enter Layer 2 VPN (L2VPN) configuration mode and configure global L2VPN commands, use the
l2vpn command in global configuration mode. To remove any global L2VPN configurations, use the
no form of this command.
l2vpn
no l2vpn
Syntax Description
This command has no arguments or keywords.
Command Default
No global L2VPN commands are configured.
Command Modes
Global configuration (config)
Command History
Release
Modification
Cisco IOS XE Release 3.7S
This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support.
15.3(1)S
This command was integrated into Cisco IOS release 15.3(1)S.
Examples
The following example shows how to enter L2VPN configuration mode and configure a Layer 2 router ID:
To create a template of pseudowire type-length-value (TLV) parameters to be used in a Multiprotocol Label Switching-Transport Profile (MPLS-TP) configuration, use the
l2vpn pseudowire tlv template command in global configuration mode. To remove the template, use the
no form of this command.
l2vpn pseudowire tlvtemplatetemplate-name
nol2vpn pseudowire tlvtemplatetemplate-name
Syntax Description
template-name
Name of the TLV template.
Command Default
Template for pseudowire TLV parameters is not created.
Command Modes
Global configuration (config)
Command History
Release
Modification
Cisco IOS XE Release 3.7S
This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the
pseudowire tlv template in future releases.
15.3(1)S
This command was integrated in Cisco IOS Release 15.3(1)S.
Usage Guidelines
This command will replace the
pseudowire tlv template in future releases.
Examples
The following example shows how to create a TLV template named tlv3:
Specifies a TLV template to be used as part of local interface configuration.
l2vpn pseudowire static-oam class
To create a Layer 2 VPN (L2VPN) Operation, Administration, and Maintenance (OAM) class and specify the timeout intervals, use the
l2vpn pseudowire static-oamclass command in global configuration mode. To remove the specified class, use the
no form of this command.
l2vpn pseudowire static-oamclassclass-name
nol2vpn pseudowire static-oamclassclass-name
Syntax Description
class-name
Name of the static pseudowire OAM class.
Command Default
Static pseudowire OAM classes are not created.
Command Modes
Global configuration (config)
Command History
Release
Modification
Cisco IOS XE Release 3.7S
This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the
pseudowire-static-oam class
command in future releases.
15.3(1)S
This command was integrated in Cisco IOS Release 15.3(1)S.
Usage Guidelines
Use the
l2vpn pseudowire static-oamclass command to create an OAM class and enter static pseudowire OAM configuration mode, from which you can enter timeout intervals.
Examples
The following example shows how to create a static OAM class named oam-class3 and enter static pseudowire OAM configuration mode:
Creates an OAM class and specifies the timeout intervals
statusprotocolnotificationstatic
Invokes a specified class as part of the static pseudowire.
l2vpn subscriber
To create a Layer 2 VPN (L2VPN) subscriber authorization group and enter L2VPN subscriber group mode, use the
l2vpnsubscriber command in global configuration mode. To remove the L2VPN subscriber authorization group, use the
no form of this command.
l2vpnsubscriberauthorizationgroupgroup-name
nol2vpnsubscriberauthorizationgroupgroup-name
Syntax Description
authorizationgroupgroup-name
Specifies the name of the L2VPN subscriber authorization group.
Command Default
An L2VPN subscriber authorization group is not created.
Command Modes
Global configuration (config)
Command History
Release
Modification
Cisco IOS XE Release 3.7S
This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the
l2 subscriber command in future releases.
15.3(1)S
This command was integrated in Cisco IOS Release 15.3(1)S.
Usage Guidelines
Use the
l2vpnsubscriber command to create a named service authorization group and enter L2VPN subscriber group mode.
Define multiple L2VPN subscriber authorization groups on the router. Each group defines a set of Any Transport over MPLS (AToM) peers using the peer’s Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) router ID (IP address or IP address network) and virtual circuit (VC) ID or range. You must be sure to define mutually exclusive service authorization groups.
Use configuration commands available in L2VPN subscriber group mode to enable an AToM or label advertisement to be used for First Sign of Life (FSOL) processing.
When an AToM LDP label advertisement is received and there is a matching group, the Intelligent Services Gateway (ISG) control policy map is executed and the AAA attributes for the corresponding xconnect is downloaded from RADIUS. Thus, a dynamic xconnect is provisioned for the peer provider edge (PE). Use the
showderived-configinterface command to see the details of the xconnect that is downloaded.
To provide a description for the L2VPN subscriber authorization group, use the
description command in L2VPN subscriber group mode.
Examples
The following example shows how to create a subscriber authorization group:
Device(config)# l2vpn subscriber authorization group group1
Related Commands
Command
Description
description (l2vpn)
Provides a description of the cross connect in an L2VPN multisegment pseudowire.
l2 subscriber
Creates an L2 subscriber authorization group and enter L2 subscriber group mode.
peer
Defines the target LDP PE peer information.
pseudowire(Layer2)
Defines the maximum and watermark limits for pseudowires from a peer PE device.
service-policytypecontrol(Layer2)
Attaches an ISG control service policy to an L2 subscriber authorization group.
l2vpn vfi context
To establish a Layer 2 VPN (L2VPN) virtual forwarding interface (VFI) between two or more separate networks, use the
l2vpn vfi context command in global configuration mode. To disable the connection, use the
no form of this command.
l2vpnvficontextname
nol2vpnvficontextname
Syntax Description
name
Name of the VFI context.
Command Default
L2VPN VFIs are not established.
Command Modes
Global configuration (config)
Command History
Release
Modification
Cisco IOS XE Release 3.7S
This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the
l2 vfi command in future releases.
Usage Guidelines
Use the
l2vpn vfi context command to establish a VFI for specifying core-facing pseudowires in a Virtual Private LAN Services (VPLS). The VFI represents an emulated LAN or a VPLS forwarder from the VPLS architectural model when using an emulated LAN interface.
Examples
The following example shows how to establish an L2VPN VFI context:
Device(config)# l2vpn vfi context vfi1
Related Commands
Command
Description
l2 vfi
Establishes an L2 VFI.
l2vpn xconnect context
To create a Layer 2 VPN (L2VPN) cross connect context and enter xconnect configuration mode, use the
l2vpn xconnect context command in global configuration mode. To remove the connection, use the
no form of this command.
l2vpnxconnect
contextcontext-name
nol2vpnxconnect
contextcontext-name
Syntax Description
context-name
Name of the cross connect context.
Command Default
L2VPN cross connections are not created.
Command Modes
Global configuration (config)
Command History
Release
Modification
Cisco IOS XE Release 3.7S
This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the
l2 vfi (point to point),
connect (L2VPN local switching), and
xconnect commands in future releases.
15.3(1)S
This command was integrated in Cisco IOS Release 15.3(1)S.
Usage Guidelines
Use the
l2vpn xconnect context command to define a cross connect context that specifies the two members in Virtual Private Wire Service (VPWS)—attachment circuit to pseudowire, pseudowire to pseudowire (multisegment pseudowire), or attachment circuit to attachment circuit (local connection). The type of members specified, attachment circuit interface or pseudowire, automatically define the type of L2VPN service.
Examples
The following example shows how to establish an L2VPN cross connect context:
Device(config)# l2vpn xconnect context con1
Device(config-xconnect)# interworking ip
Related Commands
Command
Description
l2 vfi point to point
Establishes a point-to-point L2 VFI between two separate networks.
label (pseudowire)
To configure an Any Transport over MPLS (AToM) static pseudowire connection by defining local and remote circuit labels, use the
label command in interface configuration mode. To remove the local and remote pseudowire labels, use the
no form of this command.
An unused static label that is within the range defined by the
mpls label range command.
remote-pseudowire-label
The value of the peer provider edge router’s local pseudowire label.
Command Default
Circuit labels are not configured.
Command Modes
Interface configuration (config-if)
Command History
Release
Modification
Cisco IOS XE Release 3.7S
This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the
mpls label command in future releases.
15.3(1)S
This command was integrated in Cisco IOS Release 15.3(1)S.
Usage Guidelines
The
label command is mandatory when configuring AToM static pseudowires and must be configured at both ends of the connection.
The
label command checks the validity of the local pseudowire label and generates an error message if the label is invalid.
Examples
The following example shows configuration of an AToM static pseudowire connection on the local device:
Enables the MPLS control word in an AToM dynamic pseudowire connection.
mpls label
Configures an AToM static pseudowire connection by defining local and remote circuit labels.
mpls label range
Configures the range of local labels available for use on packet interfaces.
show l2vpn atom vc
Displays information about AToM VCs and AToM static pseudowires that have been enabled to route Layer 2 packets on a router.
list
To show all or part of the explicit path or paths, use the
list command in IP explicit path configuration mode.
list [starting-index-number]
Syntax Description
starting-index-number
(Optional) Index number at which the explicit path(s) will start to be displayed. The range is 1 to 65535.
Command Default
Explicit paths are not shown.
Command Modes
IP explicit path configuration
Command History
Release
Modification
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T.
12.0(10)ST
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Examples
The following example shows how to list the explicit path:
Router(cfg-ip-expl-path)# list
Explicit Path name path1:
1:next-address 10.0.0.1
2:next-address 10.0.0.2
The following example shows how to list the explicit path starting at index number 2:
Router(cfg-ip-expl-path)# list 2
Explicit Path name path1:
2:next-address 10.0.0.2
Router(cfg-ip-expl-path)#
Related Commands
Command
Description
append-after
Inserts the new path entry after the specified index number. Commands might be renumbered as a result.
index
Inserts or modifies a path entry at a specific index.
ip explicit-path
Enters the command mode for IP explicit paths, and creates or modifies the specified path.
next-address
Specifies the next IP address in the explicit path.
show ip explicit-paths
Displays the configured IP explicit paths.
list (LSP Attributes)
To display the contents of a label switched path (LSP) attribute list, use the
list command in LSP Attributes configuration mode.
list
Syntax Description
This command has no arguments or keywords.
Command Default
Contents of an LSP attribute list is not displayed.
Command Modes
LSP Attributes configuration (config-lsp-attr)
Command History
Release
Modification
12.0(26)S
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines
This command displays the contents of the LSP attribute list. You can display each of the following configurable LSP attributes using the
list command: affinity, auto-bw, bandwidth, lockdown, priority, protection, and record-route.
Examples
The following example shows how to display the contents of an LSP attribute list identified with the string priority:
To enable load
balancing of traffic across multiple core interfaces using equal cost
multipaths (ECMP) for Virtual Private LAN Services (VPLS), use the
load-balance
flow command in the appropriate configuration mode. To disable
load balancing of VPLS traffic, use the
no form of this
command.
(Optional) Specifies the Ethernet pseudowire flow classification.
dst-mac
(Optional) Specifies the destination MAC address.
src-dst-mac
(Optional) Specifies the source and destination MAC address.
src-mac
(Optional) Specifies the source MAC address.
Command Default
Load balancing is
disabled.
Command Modes
Interface configuration (config-if)
Pseudowire class configuration (config-pw-class)
Template configuration (config-template)
Command History
Release
Modification
12.2(33)SXI4
This
command was introduced.
Cisco IOS
XE Release 3.4S
This
command was integrated into Cisco IOS XE Release 3.4S. Support was added for
the Cisco ASR 1000 Series Routers.
Cisco IOS
XE Release 3.7S
This
command was modified as part of the MPLS-based Layer 2 VPN (L2VPN) command
modifications for cross-OS support. This command was made available in
interface configuration and template configuration modes.
15.1(1)SY
This
command was integrated into Cisco IOS Release 15.1(1)SY.
15.3(1)S
This
command was integrated into Cisco IOS Release 15.3(1)S.
Usage Guidelines
This command
enables ECMP load balancing only for the pseudowire for which it was
configured.
Examples
The following
example shows how to configure a pseudowire and enable flow-based load
balancing:
Specifies an encapsulation type for tunneling Layer 2 traffic over a
pseudowire.
flow-label enable
Enables
the imposition and disposition of flow labels.
load-balance flow-label
Enables the use of flow labels to load balance traffic
across multiple core interfaces using ECMP for VPLS.
load-balance
flow-label
To balance the
load based on flow labels, use the
load-balance
flow-label command in pseudowire class configuration mode. To
disable flow-label-based load balancing, use the
no form of
this command.
load-balanceflow-label
{ both | receive | transmit }
noload-balanceflow-label
Syntax Description
both
Inserts
or discards flow labels on transmit or receive.
receive
Discards
flow labels on receive.
transmit
Inserts
flow labels on transmit.
Command Default
Load-balancing
flow labels are disabled.
Command Modes
Pseudowire class configuration (config-pw-class)
Command History
Release
Modification
Cisco
IOS XE Release 3.11S
This
command was introduced.
Examples
The following
example shows how to configure a pseudowire and enable flow-based labels for
load balancing:
The following
example shows how to configure a template and enable flow-based labels for load
balancing in template configuration mode:
Device(config)# template type pseudowire fatpw
Device(config-pw-class)# encapsulation mpls
Device(config-pw-class)# load-balance flow
Device(config-pw-class)# load-balance flow-label both
Device(config-pw-class)# end
Device(config)# interface pseudowire 100
Device(config-if)# source template type pseudowire fatpw
Device(config-if)# encapsulation mpls
Device(config-if)# neighbor 10.1.1.1 1
Device(config-if)# signaling protocol ldp
Related Commands
Command
Description
encapsulation
(pseudowire)
Specifies an encapsulation type for tunneling Layer 2 traffic over a
pseudowire.
flow-label enable
Enables the imposition and disposition of flow labels.
load-balance flow
Enables load balancing of traffic across multiple core
interfaces using ECMP for VPLS.
local interface
To specify the pseudowire type when configuring pseudowires in a Mutliprotocol Label Switching Transport Protocol (MPLS-TP) network, use the localinterface command in virtual forwarding interface (VFI) neighbor configuration mode. This command enters enters VFI neighbor interface configuration mode. To disble the pseudowire type, use the no form of this command.
localinterfacepseudowire-type
nolocalinterfacepseudowire-type
Syntax Description
pseudowire-type
Psuedowire type by its number in hexadecimal format:
01 Frame Relay DLCI (Martini Mode)
02 ATM AAL5 SDU VCC transport
03 ATM transparent cell transport
04 Ethernet Tagged Mode
05 Ethernet
06 HDLC
07 PPP
08 SONET/SDH Circuit Emulation Service Over MPLS
09 ATM n-to-one VCC cell transport
0A ATM n-to-one VPC cell transport
0B IP Layer2 Transport
0C ATM one-to-one VCC Cell Mode
0D ATM one-to-one VPC Cell Mode
0E ATM AAL5 PDU VCC transport
0F Frame-Relay Port mode
10 SONET/SDH Circuit Emulation over Packet
11 Structure-agnostic E1 over Packet
12 Structure-agnostic T1 (DS1) over Packet
13 Structure-agnostic E3 over Packet
14 Structure-agnostic T3 (DS3) over Packet
15 CESoPSN basic mode
16 TDMoIP AAL1 Mode
17 CESoPSN TDM with CAS
Command Default
No pseudowire type is defined.
Command Modes
VFI neighbor configuration
Command History
Release
Modification
15.1(1)SA
This command was introduced.
15.1(3)S
This command was integrated.
Usage Guidelines
The VC types 04 and 05 are supported.
Examples
The following example sets the pseudowire VC type to Ethernet and enters VFI neighbor interface configuration mode:
Router(config-vfi-neighbor)# local interface 5
R1(config-vfi-neighbor-interface)# tlv mtu 1 4 1500
lockdown (LSP Attributes)
To disable reoptimization of the label switched path (LSP), use the
lockdown command in LSP Attributes configuration mode. To reenable reoptimization, use the
no form of this command.
lockdown
nolockdown
Syntax Description
This command has no arguments or keywords.
Command Default
Reoptimization of the LSP is enabled.
Command Modes
LSP Attributes configuration (config-lsp-attr)
Command History
Release
Modification
12.0(26)S
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines
Use this command to set up in an LSP attribute list the disabling of reoptimization of an LSP triggered by a timer, or the issuance of the
mplstraffic-engreoptimizecommand, or a configuration change that requires the resignalling of an LSP.
To associate the LSP lockdown attribute and the LSP attribute list with a path option for an LSP, you must configure the
tunnelmplstraffic-engpathoption command with the
attributesstring keyword and argument, where
string is the identifier for the specific LSP attribute list.
Examples
The following example shows how to configure disabling of reoptimization in an LSP attribute list:
To enable the display of Multiprotocol Label Switching (MPLS)
transport profile (TP) events, use the
logging command in MPLS-TP configuration
mode. To disable the display of MPLS-TP events, use the
no form of this command.
logging
{ config-change | events }
nologging
{ config-change | events }
Syntax Description
config-change
Displays events related to any configuration change to an
MPLS-TP tunnel, link, or midpoint label switched path (LSP).
events
Displays events related to any interface or LSP state
changes.
Command Default
Logging is not enabled.
Command Modes
MPLS-TP configuration mode (config-mpls-tp)
Command History
Release
Modification
15.1(3)S
This command was introduced.
Usage Guidelines
The following events are captured in the logs:
MPLS-TP Tunnel Down or MPLS-TP Tunnel Up:
%MPLS-TP-3-UPDOWN: Tunnel-tp<Tunnel_Num>, changed state to (Up | Down | AdminDown)
%LINK-3-UPDOWN: Interface Tunnel-tp<Tunnel_Num>, changed state to (Up | Down)
%LINK-5-CHANGED: Interface Tunnel-tp<Tunnel_Num>, changed state to administratively down
The following example enables the display of interface or LSP state
changes:
Router(config-mpls-tp)# logging events
Related Commands
Command
Description
debugmplstp
Enables the display of MPLS-TP error messages.
logging pseudowire status
To enable system logging (syslog) reporting of pseudowire status events, use the
logging pseudowire status command in L2VPN configuration mode. To disable syslog reporting of pseudowire status events, use the
no form of this command.
loggingpseudowirestatus
nologgingpseudowirestatus
Syntax Description
This command has no arguments or keywords.
Command Default
Syslog reporting of pseudowire status events is disabled.
Command Modes
L2VPN configuration (config-l2vpn)
Command History
Release
Modification
Cisco IOS XE Release 3.7S
This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the
xconnect logging pseudowire status command in future releases.
15.3(1)S
This command was integrated in Cisco IOS Release 15.3(1)S.
Examples
The following example shows how to enable syslog reporting of pseudowire status events:
Device(config)# l2vpn
Device(config-l2vpn)# logging pseudowire status
Related Commands
Command
Description
xconnect logging pseudowire status
Enables syslog reporting of pseudowire status events.
logging redundancy
To enable system message log (syslog) reporting of xconnect redundancy status events, use the
loggingredundancy command in L2VPN configuration mode. To disable syslog reporting of xconnect redundancy status events, use the
no form of this command.
loggingredundancy
nologgingredundancy
Syntax Description
This command has no arguments or keywords.
Command Default
Syslog reporting of the status of the xconnect redundancy group is disabled.
Command Modes
L2VPN configuration (config-l2vpn)
Command History
Release
Modification
Cisco IOS XE Release 3.7S
This command was introduced as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command will replace the
xconnect logging redundancy command in future releases.
15.3(1)S
This command was integrated in Cisco IOS Release 15.3(1)S.
Examples
The following example shows how to enable syslog reporting of the status of the xconnect redundancy group and shows the messages that are generated during switchover events: