- Finding Feature Information
- Restrictions for MPLS LDP Inbound Label Binding Filtering
- Information about MPLS LDP Inbound Label Binding Filtering
- How to Configure MPLS LDP Inbound Label Binding Filtering
- Configuration Examples for MPLS LDP Inbound Label Binding Filtering
- Additional References
- Feature Information for MPLS LDP Inbound Label Binding Filtering
- Glossary
MPLS LDP Inbound Label Binding Filtering
The MPLS LDP Inbound Label Binding Filtering feature supports inbound label binding filtering. You can use the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) feature to configure access control lists (ACLs) for controlling the label bindings a label switch router (LSR) accepts from its peer LSRs.
- Finding Feature Information
- Restrictions for MPLS LDP Inbound Label Binding Filtering
- Information about MPLS LDP Inbound Label Binding Filtering
- How to Configure MPLS LDP Inbound Label Binding Filtering
- Configuration Examples for MPLS LDP Inbound Label Binding Filtering
- Additional References
- Feature Information for MPLS LDP Inbound Label Binding Filtering
- Glossary
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 Inbound Label Binding Filtering
Inbound label binding filtering does not support extended ACLs; it only supports standard ACLs.
Information about MPLS LDP Inbound Label Binding Filtering
MPLS LDP Inbound Label Binding Filtering Benefit
The MPLS LDP Inbound Label Binding Filtering feature may be used to control the amount of memory used to store LDP label bindings advertised by other routers. For example, in a simple MPLS Virtual Private Network (VPN) environment, the VPN provider edge (PE) routers may require LSPs only to their peer PE routers (that is, they do not need LSPs to core routers). Inbound label binding filtering enables a PE router to accept labels only from other PE routers.
How to Configure MPLS LDP Inbound Label Binding Filtering
- Configuring MPLS LDP Inbound Label Binding Filtering
- Verifying that MPLS LDP Inbound Label Bindings are Filtered
Configuring MPLS LDP Inbound Label Binding Filtering
Perform this task to configure a router for inbound label filtering.
The following configuration allows the router to accept only the label for prefix 192.168.1.1 from LDP neighbor router 10.12.12.12.
DETAILED STEPS
Verifying that MPLS LDP Inbound Label Bindings are Filtered
If inbound filtering is enabled, perform the following tasks to verify that inbound label bindings are filtered.
DETAILED STEPS
Configuration Examples for MPLS LDP Inbound Label Binding Filtering
Configuring MPLS LDP Inbound Label Binding Filtering Example
In the following example, the mpls ldp neighbor labels accept command is configured with an access control list to filter label bindings received on sessions with the neighbor 10.110.0.10.
Label bindings for prefixes that match 10.b.c.d are accepted, where b is less than or equal to 63, and c and d can be any integer between 0 and 128. Other label bindings received from 10.110.0.10 are rejected.
Router# configure terminal Router(config)# access-list 1 permit 10.63.0.0 0.63.255.255 Router(config)# mpls ldp neighbor 10.110.0.10 labels accept 1 Router(config)# end
In the following example, the show mpls ldp bindings neighbor command displays label bindings that were learned from 10.110.0.10. This example verifies that the LIB does not contain label bindings for prefixes that have been excluded.
Router# show mpls ldp bindings neighbor 10.110.0.10 tib entry: 10.2.0.0/16, rev 4 remote binding: tsr: 10.110.0.10:0, tag: imp-null tib entry: 10.43.0.0/16, rev 6 remote binding: tsr: 10.110.0.10:0, tag: 16 tib entry: 10.52.0.0/16, rev 8 remote binding: tsr: 10.110.0.10:0, tag: imp-null
Additional References
The following sections provide additional references related to MPLS LDP inbound label binding filters.
Related Documents
Related Topic |
Document Title |
---|---|
Configuration information for MPLS LDP |
"MPLS Label Distribution Protocol (LDP) " chapter in the Cisco IOS XE Multiprotocol Label Switching Configuration Guide |
MPLS LDP commands |
Cisco IOS Multiprotocol Label Switching Command Reference |
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 Label Distribution Protocol MIB ( draft-ietf-mpls-ldp-08.txt) |
To locate and download MIBs for selected platforms, Cisco IOS XE software 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 Inbound Label Binding Filtering
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 Inbound Label Bonding Filtering |
Feature Name |
Releases |
Feature Information |
---|---|---|
MPLS LDP Inbound Label Binding Filtering |
Cisco IOS XE Release 2.1
|
The MPLS LDP Inbound Label Binding Filtering feature supports inbound label binding filtering. You can use the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) feature to configure access control lists (ACLs) for controlling the label bindings a label switch router (LSR) accepts from its peer LSRs. In Cisco IOS XE Release 2.1, support was added for the Cisco ASR 1000 Series Aggregation Services Routers. The following commands were introduced or modified: clear mpls ldp neighbor, mpls ldp neighbor labels accept, show mpls ldp neighbor. |
Glossary
CE router --customer edge router. A router that is part of a customer network and that interfaces to a provider edge (PE) router.
inbound label binding filtering --Allows LSRs to control which label bindings it will accept from its neighboring LSRs. Consequently, an LSR does not accept or store some label bindings that its neighbors advertise.
label --A short fixed-length identifier that tells switching nodes how to forward data (packets or cells).
label binding --An association between a destination prefix and a label.
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.