The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco NX-OS Multiprotocol Label Switching commands that begin with M.
To configure a classification criteria, use the match command. To return to the default setting, use the no form of this command.
match [not] mpls experimental topmost exp-list
no match [not] mpls experimental topmost exp-list
List that can contain values and ranges. The range is from 0 to 7. |
|
|
---|---|
This example shows how to specify that the packets should be matched (or not) on the 3-bit experimental (EXP) field in the outermost (topmost) MPLS label in the MPLS header:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To configure the maximum number of routes that can be stored in the virtual routing and forwarding (VRF) route table, use the maximum routes command. To return to the default setting, use the no form of this command.
maximum routes max-routes [threshold-value [reinstall threshold-value] | warning-only]
no maximum routes max-routes [threshold-value [reinstall threshold-value] | warning-only]
Address-family configuration mode
|
|
---|---|
This example shows how to configure the maximum number of routes that can be stored in the VRF route table:
This example shows how to reinstall the previously rejected route that exceeded the maximum route limit:
|
|
---|---|
To specify the maximum number of BGP VPNv4 multipaths for both eBGP and iBGP paths, use the maximum-paths eibgp command. To remove the multipaths, use th no form of this command.
maximum-paths eibgp parallel-paths
no maximum-paths eibgp [parallel-paths]
Maximum number of multipaths for both eBGP and iBGP paths. The default value is 1. |
Global configuration mode (config)
network-admin
vdc-admin
network-operator
vdc-operator
|
|
---|---|
Use this command on PE devices and Route Reflectors in an MPLS topology.
This example shows how to specify the maximum number of BGP VPNv4 multipaths for both eBGP and iBGP paths:
|
|
---|---|
To specify that a shared-tree [(*,G)] entry should be created for a default multicast distribution tree (MDT) when the default MDT group is in PIM ASM mode, use the mdt asm-use-shared-tree
|
|
---|---|
This example shows how to configure the shared-tree [(*,G)] entry should be created for the default MDT when the default MDT group is in PIM ASM mode:
|
|
---|---|
To configure a range of group addresses that are used for data multicast distribution trees (MDTs), use the mdt data command.
mdt data mdt -group-prefix [threshold threshold-value] [route-map policy-name]
|
|
---|---|
This example shows how to configure the the range of group address used for data MDTs:
|
|
---|---|
To configure the range of group address used for data multicast distribution trees (MDTs), use the mdt data bidir-enable command.
|
|
---|---|
This command allows the user to override the default behavior that is, create data MDTs for bidir routes as well.
This example shows how to configure the the range of group addresses used for data MDTs:
|
|
---|---|
To configure the default multicast distribution tree (MDT) for a virtual routing and forwarding (VRF), use the mdt default command. To return to the default settings, use the no form of the command.
|
|
---|---|
This example shows how to configure the default MDT for a VRF:
|
|
---|---|
To enforce the use of multicast distribution tree (MDT) subsequent address family identifiers (SAFI) for a virtual routing and forwarding instance (VRF), use the mdt enforce-bgp-mdt-safi command. To interoperate with peers that do not support MDT SAFI, use the no form of the command. When the no form is used, initially only the (*,G) entry for the default MDT group is populated if it falls within the Any Source Multicast (ASM) range. Then later, based on traffic, the (S,G) entries are learned like regular ASM routes.
|
|
---|---|
This example shows how to configure MDT to interoperate with peers that do not support MDT SAFI:
|
|
---|---|
Displays detailed information of the BGP advertisement for MVPN MDT SAFI. |
To configure the maximum transmission unit (MTU) associated with the multicast tunnel interfaces created for the default and data multicast distribution tree (MDT) groups, use the mdt mtu command.
|
|
---|---|
This example shows how to configure the maximum transmission unit (MTU) associated with the multicast tunnel interfaces created for the default and data MDT groups:
|
|
---|---|
To configure the hello interval used between peers, use the mdt pim hello-interval command.
mdt ip pim hello-interval interval
no mdt ip pim hello-interval interval
Interval in milliseconds. The range is from 3000 to 18724286. |
|
|
---|---|
This example shows how to configure the hello interval used between peers:
|
|
---|---|
To configure the PIM periodic interval associated with join or prune packet transmission over the default multicast distribution tree (MDT) tunnel interface, use the mdt pim jp-interval command. To return to the default settings, use the no form of the command.
no mdt pim jp-interval interval
|
|
---|---|
This example shows how to configure the PIM periodic interval associated join packet transmission over the default MDT tunnel interface:
|
|
---|---|
To configure the interface that is used to set the multicast virtual private network (VPN) data multicast distribution tree (MDT) source address, use the mdt source command.
Interface used to set the multicast VPN data multicast distribution tree (MDT) source address. |
|
|
---|---|
This example shows how to configure the interface that is used to set the multicast VPN data multicast distribution tree (MDT) source address:
|
|
---|---|
To add an active Ethernet AC, with or without an Ethernet Flow Point (EFP), to the context, use the member command. To delete the member configuration, use the no form of this command.
member interface-type {ip-address ip-address | ethenet slot/port-number | port-channel port-channel- number | pseudowire pw-id} [service-instance service-instance-id] [group group-name] [priority number]
no member interface-type {ip-address ip-address | ethenet slot/port-number | port-channel port-channel- number | pseudowire pw-id} [service-instance service-instance-id] [group group-name] [priority number]
config-xconnect configuration mode
|
|
---|---|
This example shows how to add an active Ethernet AC, with or without an EFP, to the context:
To specify the devices that form a point-to-point Layer 2 VPN (L2VPN) Virtual Forwarding Interface (VFI) connection, use the member encapsulation mpls command.
member ip-address encapsulation mpls
|
|
---|---|
This example shows how to specify the devices that form a point-to-point L2VPN VFI connection:
To add an active pseudowire to the XConnect context, use the member pseudowire command. To remove the active pseudowire configuration, use the no form of this command.
member pseudowire pw-id [group group-name] [priority number]
no member pseudowire pw-id [group group-name] [priority number]
|
|
---|---|
This example shows how to add an active pseudowire to the XConnect context:
To bind a virtual forwarding interface (VFI) to a bridge domain, use the member vfi command.
VFI ID. The VFI ID can be any alphanumeric, case-sensitive up to 100 characters. |
|
|
---|---|
This example shows how to bind a VFI to this bridge domain:
To enable IP over Multiprotocol Label Switching (MPLS), use the mpls ip command.
|
|
---|---|
This example shows how to enable IP over MPLS:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To enable the LDP over an MPLS TE tunnel, use the mpls ip command.
|
|
---|---|
This example shows how to configure the IP TTl propagation over MPLS:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To enable MPLS on the specified interface. use mpls ip forwarding command.
|
|
---|---|
To allow Multiprotocol Label Switching (MPLS) forwarding for the IP default route, use the mpls ip default-route command. To revert to the default settings, use the no form of the command.
LDP configuration interface mode
|
|
---|---|
This example shows how to allow MPLS forwarding for the IP default route:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To configure the Multiprotocol Label Switching (MPLS) label range for a static label assignment, use the mpls label range command. To return to the default setting, use the no form of this command.
mpls label range min-value max-value [static min-static-value max-static-value]
no mpls label range min-value max-value [static min-static-value max-static-value]
(Optional) Specifies the block of labels for static bindings. |
|
|
|
---|---|
This example shows how to reserve a range of labels for static label assignment:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To enable Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) autoconfiguration for all level-1, all level-2, or all level-1 and level-2 IS-IS interfaces, use the mpls ldp autoconfig command. To return to the default setting, use the no form of this command.
mpls ldp autoconfig {level-1 | level-1-2 | level-2}
no mpls ldp autoconfig {level-1 | level-1-2 | level-2}
|
|
---|---|
This example shows how to enable MPLS LDP autoconfiguration for all level-1, all level-2, or all level-1 and level-2 IS-IS interfaces:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To enable Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) autoconfiguration for all Open Shortest Path First (OSPF) interfaces, use the mpls ldp autoconfig area command. To return to the default setting, use the no form of this command.
mpls ldp autoconfig area area-id
no mpls ldp autoconfig area area-id
Area ID as an integer or IP address. The range is from 0 to 4294967295. |
|
|
---|---|
This example shows how to enable MPLS LDP autoconfiguration for all OSPF interfaces:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To configure the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP), use the mpls ldp configuration command.
|
|
---|---|
When MPLS LDP is disabled on the device, no LDP commands are available.
This example shows how to configure MPLS LDP:
|
|
---|---|
Enables Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) Interior Gateway Protocol (IGP) synchronization for all IS-IS interfaces. |
To configure the transport address that is advertised in the Label Distribution Protocol (LDP) discovery hello messages sent on an interface, use the mpls ldp discovery transport-address command. To return to the default setting, use the no form of this command.
mpls ldp discovery transport-address {ip-address | interface}
no mpls ldp discovery transport-address {ip-address | interface}
Specifies that the interface IP address be advertised as the transport address. |
|
|
---|---|
This example shows how to configure the transport address that is advertised in the LDP discovery hello messages sent on an interface:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To enable the switch to protect the Label Distribution Protocol (LDP) bindings and Multiprotocol Label Switching (MPLS) forwarding state during a disruption in service, use the mpls ldp graceful-restart command.
|
|
---|---|
This example shows how to enable the switch to protect the LDP bindings and MPLS forwarding state during a disruption in service:
|
|
---|---|
Displays the graceful-restart parameters for a router’s sessions with its LDP neighbors. |
To enable the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) for the specified interface, use the mpls ldp igp autoconfig command. To return to the default setting, use the no form of this command.
|
|
---|---|
This example shows how to enable MPLS LDP for the specified interface:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To configure a delay time for Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) Interior Gateway Protocol (IGP) synchronization on the specified interface, use the mpls ldp igp sync command. To return to the default setting, use the no form of this command.
mpls ldp igp sync [delay seconds]
no mpls ldp igp sync [delay seconds]
(Optional) Specifies LDP to IGP sync achieved notification delay time. |
|
(Optional) Display in seconds. The range is from 5 to 60 seconds. |
|
|
---|---|
The no mpls ldp igp sync delay command sets the delay time to 0 seconds but leaves the MPLS LDP and IGP synchronization enabled.
This example shows how to configure a delay time for the MPLS LDP and IGP synchronization on the specified interface:
|
|
---|---|
Enables Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) Interior Gateway Protocol (IGP) synchronization for all IS-IS interfaces. |
To enable Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) and Interior Gateway Protocol (IGP) synchronization for all Open Shortest Path First (OSPF) interfaces, use the mpls ldp sync command. To return to the default setting, use the no form of this command.
|
|
---|---|
This example shows how to enable MPLS LDP and IGP syncronization for all OSPF interfaces:
|
|
---|---|
Allows Label Distribution Protocol (LDP) Interior Gateway Protocol (IGP) Synchronization on this interface. |
To configure MPLS Operations and Management (OAM) for customizing the default behavior of echo packets, use the mpls oam command. To return to the default setting, use the no form of this command.
|
|
---|---|
This example shows how to configure MPLS OAM:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To configure the static binding of labels to IPv4 prefixes, use the mpls static binding ipv4 command. To return to the default setting, use the no form of this command.
mpls static binding ipv4 prefix mask {label | input label | output nexthop {explicit-null | implicit-null | label}}
no mpls static binding ipv4 prefix mask {label | input label | output nexthop {explicit-null | implicit-null | label}}
|
|
---|---|
This example shows how to configure the static binding of labels to IPv4 prefixes:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To configure the Multiprotocol Label Switching (MPLS) static binding of labels to the IPv4 destination VPN routing prefix, use the mpls static binding ipv4 vrf command. To return to the default setting, use the no form of this command.
mpls static binding ipv4 vrf vpn-name prefix mask {input label | label}
no mpls static binding ipv4 vrf vpn-name prefix mask {input label | label}
|
|
---|---|
You must configure the MPLS VPN and VRFs before creating VRF-aware static labels.
This example shows how to configure static label bindings input and output labels for several prefixes:
|
|
---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
To override the Interior Gateway Protocol (IGP) administrative weight (cost) of the link as used in traffic engineering (TE) path calculations, use the mpls traffic-eng administrative-weight command. To restore the system to its default condition, use the no form of this command.
mpls traffic-eng administrative-weight weight
no mpls traffic-eng administrative-weight weight
The TE link administrative weight defaults to the IGP cost of the link
|
|
---|---|
This example shows how to override the IGP administrative weight (cost) of the link:
|
|
---|---|
To turn on the Multiprotocol Label Switching (MPLS) traffic engineering (TE) for the indicated Open Shortest Path First (OSPF) area, use the mpls traffic-eng area command. To return to the default setting, use the no form of this command.
no mpls traffic-eng area area-id
|
|
---|---|
This example shows how to turn on MPLS TE for the indicated OSPF area:
|
|
---|---|
To set the user-defined interface attribute flags, use the mpls traffic-eng attribute-flags command. To return to the default setting, use the no form of this command.
mpls traffic-eng attribute-flags value
no mpls traffic-eng attribute-flags
Attribute flags. Typically entered in the range 0x0 - 0xffffffff. |
|
|
---|---|
This example shows how to set the user-defined interface attribute flags:
|
|
---|---|
To assign one or more backup tunnels to a protected interface, use the mpls traffic-eng backup-path command. To restore the system to its default condition, use the no form of this command.
mpls traffic-eng backup-path tunnel-te interface number
no mpls traffic-eng backup-path tunnel-te interface number
Enter this command on the interface to be protected (Link Protection), or on the interface whose downstream node is being protected (Node Protection). You can enter this command multiple times to select multiple backup tunnels for a given protected interface. An unlimited number of backup tunnels can be assigned to protect an interface. The only limitation is memory. By entering this command on a physical interface, LSPs using this interface (sending data out of this interface) can use the indicated backup tunnels if there is a link or node failure.
|
|
---|---|
This example shows how to configure an MPLS backup for this interface:
|
|
---|---|
To allocate the Multiprotocol Label Switching (MPLS) traffic engineering (TE) bandwidth pool for the interface, use the mpls traffic-eng bandwidth command. To restore the system to its default condition, use the no form of this command.
mpls traffic-eng bandwidth [interface-kbps | percent percentage]
If neither interface-kbps nor a percentage are specified, then the bandwidth pool size defaults to 75% of the interface’s bandwidth.
|
|
---|---|
This example shows how to allocate the MPLS TE bandwidth pool for the interface:
|
|
---|---|
To configure Multiprotocol Label Switching (MPLS) traffic engineering (TE), use the mpls traffic-eng configuration command.
mpls traffic-eng configuration
|
|
---|---|
This example shows how to configure MPLS TE:
|
|
---|---|
To set the Multiprotocol Label Switching (MPLS) flooding thresholds, use the mpls traffic-eng flooding threshold command. To return to the default setting, use the no form of this command.
mpls traffic-eng flooding thresholds{down decreased reserved bw | up increased reserved bandwidth}
no mpls traffic-eng flooding thresholds{down | up}
Specifies the thresholds for decreased resource availability. |
|
Specifies the thresholds for increased resource availability. |
|
|
|
---|---|
This example shows how to specify the thresholds for decreased resource availability:
|
|
---|---|
To configure the Multiprotocol Label Switching (MPLS) traffic engineering (TE) for Intermediate System-to-Intermediate System (IS-IS), use the mpls traffic-eng level command. To return to the default setting, use the no form of this command.
mpls traffic-eng {level-1 | level-1-2 | level-2}
no mpls traffic-eng {level-1 |level-1-2 | level-2}
|
|
---|---|
You can enable MPLS for level-1, level-2 or level 1 and level-2 routers.
This example shows how to configure MPLS TE for IS-IS:
|
|
---|---|
To specify that the traffic engineering router identifier for the node is the IP address associated with a given interface, use the mpls traffic-eng router-id command. To return to the default setting, use the no form of this command.
mpls traffic-eng router-id interface
no mpls traffic-eng router-id interface
|
|
---|---|
This command is not effective until you configure the specified loopback with an IP address.
This example shows how to configured the TE router-ID to be the IP address of the loopback 0 interface:
|
|
---|---|
To enable Multiprotocol Label Switching (MPLS) traffic engineering (TE) tunnels on an interface, use the mpls traffic-eng tunnels command. To restore the system to its default condition, use the no form of this command.
|
|
---|---|
This example shows how to enable MPLS traffic engineering tunnels:
|
|
---|---|