- Finding Feature Information
- Restrictions for MPLS LDP Autoconfiguration
- Information About MPLS LDP--Autoconfiguration
- How to Configure MPLS LDP Autoconfiguration
- Configuring MPLS LDP-Autoconfiguration with OSPF Interfaces
- Disabling MPLS LDP Autoconfiguration from Selected OSPF Interfaces
- Verifying MPLS LDP Autoconfiguration with OSPF
- Configuring MPLS LDP Autoconfiguration with IS-IS Interfaces
- Disabling MPLS LDP Autoconfiguration from Selected IS-IS Interfaces
- Configuration Examples for MPLS LDP Autoconfiguration
- Additional References
- Feature Information for MPLS LDP-VRF-Aware Static Labels
MPLS LDP Autoconfiguration
The MPLS LDP Autoconfiguration feature enables you to globally configure Label Distribution Protocol (LDP) on every interface associated with a specified Interior Gateway Protocol (IGP) instance.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Restrictions for MPLS LDP Autoconfiguration
- In Cisco IOS Release 12.0(32)SY, the mpls ldp autoconfig command is supported only with OSPF. Other IGPs are not supported.
- If LDP is disabled globally, the mpls ldp autoconfigcommand fails and generates a console message explaining that LDP must first be enabled globally by means of the global mpls ip command.
- If the mpls ldp autoconfig command is configured for an IGP instance, you cannot issue the global no mpls ip command. To disable LDP, you must first issue the no mpls ldp autoconfig command.
- For interfaces running IS-IS processes, you can enable Multiprotocol Label Switching (MPLS) for each interface, using the router mode command mpls ldp autoconfig or mpls ldp igp autoconfig at the interface level.
- You specify that the default label distribution protocol is LDP for a router or for an interface. Tag Distribution Protocol (TDP) is not supported.
- The MPLS LDP Autoconfiguration feature is not supported on traffic engineering tunnel interfaces.
Information About MPLS LDP--Autoconfiguration
MPLS LDP--Autoconfiguration Overview
To enable LDP, you should configure it globally and on each interface where it is needed. Configuring LDP on many interfaces can be time consuming.
The MPLS LDP--Autoconfiguration feature enables you to globally enable LDP on every interface associated with an IGP instance. This feature is supported on OSPF and IS-IS IGPs. Further, it provides a means to block LDP from being enabled on interfaces that you do not want enabled. The goal of the MPLS LDP--Autoconfiguration feature is to make configuration easier, faster, and error free.
You issue the mpls ldp autoconfigcommand to enable LDP on each interface that is running an OSPF or IS-IS process. If you do not want some of the interfaces to have LDP enabled, you can issue the noform of the mpls ldp igp autoconfig command on those interfaces.
How to Configure MPLS LDP Autoconfiguration
- Configuring MPLS LDP-Autoconfiguration with OSPF Interfaces
- Disabling MPLS LDP Autoconfiguration from Selected OSPF Interfaces
- Verifying MPLS LDP Autoconfiguration with OSPF
- Configuring MPLS LDP Autoconfiguration with IS-IS Interfaces
- Disabling MPLS LDP Autoconfiguration from Selected IS-IS Interfaces
Configuring MPLS LDP-Autoconfiguration with OSPF Interfaces
To configure MPLS LDP-Autoconfiguration with OFPF interfaces, perform the following steps.
DETAILED STEPS
Disabling MPLS LDP Autoconfiguration from Selected OSPF Interfaces
When you issue the mpls ldp autoconfig command, all the interfaces that belong to an OSPF area are enabled for LDP. To remove LDP from some interfaces, use the no mpls ldp igp autoconfigcommand on those interfaces. The following configuration steps show how to disable LDP from some of the interfaces after they were configured with the MPLS LDP Autoconfiguration feature with the mpls ldp autoconfig command.
DETAILED STEPS
Verifying MPLS LDP Autoconfiguration with OSPF
The following steps explain how to verify the MPLS LDP Autoconfiguration feature.
DETAILED STEPS
Configuring MPLS LDP Autoconfiguration with IS-IS Interfaces
The following steps explain how to configure the MPLS LDP Autoconfiguration feature for interfaces that are running IS-IS processes.
DETAILED STEPS
Disabling MPLS LDP Autoconfiguration from Selected IS-IS Interfaces
When you issue the mpls ldp autoconfig command, all the interfaces that belong to an IS-IS process are enabled for LDP. To remove LDP from some interfaces, use the no mpls ldp igp autoconfig command on those interfaces. The following configuration steps show how to disable LDP from some of the interfaces after they were configured with the MPLS LDP Autoconfiguration feature with the mpls ldp autoconfig command.
DETAILED STEPS
Configuration Examples for MPLS LDP Autoconfiguration
The following sections show examples for the MPLS LDP Autoconfiguration feature with OSPF and IS-IS processes.
MPLS LDP Autoconfiguration with IS-IS Examples
The following example shows the configuration of the MPLS LDP Autoconfiguration feature on POS0/2 and 0/3 interfaces, which are running IS-IS processes:
configure terminal interface POS 0/2 ip address 10.0.0.1 255.0.0.1 ip router isis ! interface POS 0/3 ip address 10.1.1.1 255.0.1.0 ip router isis exit
mpls ip
mpls label protocol ldp
router isis
mpls ldp autoconfig
MPLS LDP Autoconfiguration with OSPF Example
The following configuration commands enable LDP for OSPF process 1 area 3. The mpls ldp autoconfig area 3 command and the OSPF network commands enable LDP on POS interfaces 0/0, 0/1, and 1/1. The no mpls ldp igp autoconfig command on POS interface 1/0 prevents LDP from being enabled on POS interface 1/0, even though OSPF is enabled for that interface.
configure terminal interface POS 0/0 ip address 10.0.0.1 255.0.0.0 ! interface POS 0/1 ip address 10.0.1.1 255.0.0.1 ! interface POS 1/1 ip address 10.1.1.1 255.255.0.0 ! interface POS 1/0 ip address 10.1.0.1 0.1.0.255 exit ! router ospf 1 network 10.0.0.0 0.0.255.255 area 3 network 10.1.0.0 0.0.255.255 area 3 mpls ldp autoconfig area 3 end interface POS 1/0 no mpls ldp igp autoconfig
Additional References
The following sections provide references related to the MPLS LDP Autoconfiguration feature.
Related Documents
Related Topic |
Document Title |
---|---|
MPLS commands |
Cisco IOS Multiprotocol Label Switching Command Reference |
MPLS LDP |
MPLS Label Distribution Protocol |
The MPLS LDP-IGP Synchronization feature |
MPLS LDP-IGP Synchronization |
The MPLS LDP Session Protection feature |
MPLS LDP Session Protection |
Configuring integrated IS-IS |
Integrated IS-IS Routing Protocol Overview |
Standards
Standard |
Title |
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature |
-- |
MIBs
MIB |
MIBs Link |
---|---|
MPLS LDP MIB |
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs
RFC |
Title |
---|---|
RFC 3036 |
|
RFC 3037 |
Technical Assistance
Description |
Link |
---|---|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
Feature Information for MPLS LDP-VRF-Aware Static Labels
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1 | Feature Information for MPLS LDP-VRF-Aware Static Labels |
Feature Name |
Releases |
Feature Information |
---|---|---|
MPLS LDP-VRF-Aware Static Labels |
Cisco IOS XE Release 2.1 |
The MPLS LDP-VRF-Aware Static Labels feature explains how to configure the MPLS LDP-VRF-Aware Static Labels feature and MPLS static labels. VRF-aware static labels can be used at the edge of an MPLS VPN, whereas MPLS static labels can be used only in the MPLS VPN provider core. In Cisco IOS XE Release 2.2, this feature was implemented on the Cisco ASR 1000 Series Aggregation Services Routers. The following commands were introduced or modified: debug mpls static binding, mpls label range, mpls static binding ipv4, mpls static binding ipv4 vrf, show mpls label range, show mpls static binding ipv4, and show mpls static binding ipv4 vrf. |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.