Table Of Contents
MPLS LDP Inbound Label Binding Filtering
Information about MPLS LDP Inbound Label Binding Filtering
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
Configuration Examples for MPLS LDP Inbound Label Binding Filtering
Feature Information for MPLS LDP Inbound Label Binding Filtering Feature
MPLS LDP Inbound Label Binding Filtering
Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) supports inbound label binding filtering. You can use the MPLS LDP Inbound Label Binding Filtering feature to configure access control lists (ACLs) for controlling the label bindings a label switch router (LSR) accepts from its peer LSRs.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
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
Restrictions
Inbound label binding filtering does not support extended ACLs; it only supports standard ACLs.
Information about MPLS LDP Inbound Label Binding Filtering
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
This section includes the following tasks:
•
Configuring MPLS LDP Inbound Label Binding Filtering (Required)
•
Verifying that MPLS LDP Inbound Label Bindings are Filtered (Optional)
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 25.0.0.2 from LDP neighbor router 10.12.12.12.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip access-list standard access-list-number
4.
permit {source [source-wildcard] | any} [log]
5.
exit
6.
mpls ldp neighbor [vrf vpn-name] nbr-address labels accept acl
7.
end
DETAILED STEPS
Verifying that MPLS LDP Inbound Label Bindings are Filtered
If inbound filtering is enabled, perform the following steps to verify that inbound label bindings are filtered:
Step 1
Enter the show mpls ldp neighbor command to show the status of the LDP session, including the name or number of the ACL configured for inbound filtering.
show mpls ldp neighbor [vrf vpn-name][address | interface] [detail]
Note
To display information about inbound label binding filtering, you must enter the detail keyword.
Following is sample output from the show mpls ldp neighbor command.
Router# show mpls ldp neighbor 10.12.12.12 detailPeer LDP Ident: 10.12.12.12:0; Local LDP Ident 10.13.13.13:0TCP connection: 10.12.12.12.646 - 10.13.13.13.12592State: Oper; Msgs sent/rcvd: 49/45; Downstream; Last TIB rev sent 1257Up time: 00:32:41; UID: 1015; Peer Id 0;LDP discovery sources:Serial1/0; Src IP addr: 25.0.0.2holdtime: 15000 ms, hello interval: 5000 msAddresses bound to peer LDP Ident:10.0.0.129 10.12.12.12 10.0.0.2Peer holdtime: 180000 ms; KA interval: 60000 ms; Peer state: estabLDP inbound filtering accept acl: 1Step 2
Enter the show ip access-list command to display the contents of all current IP access lists or of a specified access list.
show ip access-list [access-list-number | access-list-name]
Note
It is important that you enter this command to see how the access list is defined; otherwise, you cannot verify inbound label binding filtering.
The following command output shows the contents of IP access list 1:
Router# show ip access 1Standard IP access list 1permit 10.0.0.0, wildcard bits 0.0.0.255 (1 match)Step 3
Enter the show mpls ldp bindings command to verify that the LSR has remote bindings only from a specified peer for prefixes permitted by the access list.
Router# show mpls ldp bindingstib entry: 10.0.0.0/8, rev 4local binding: tag: imp-nulltib entry: 10.2.0.0/16, rev 1137local binding: tag: 16tib entry: 10.2.0.0/16, rev 1139local binding: tag: 17tib entry: 10.12.12.12/32, rev 1257local binding: tag: 18tib entry: 10.13.13.13/32, rev 14local binding: tag: imp-nulltib entry: 10.10.0.0/16, rev 711local binding: tag: imp-nulltib entry: 10.0.0.0/8, rev 1135local binding: tag: imp-nullremote binding: tsr: 12.12.12.12:0, tag: imp-nulltib entry: 10.0.0.0/8, rev 8local binding: tag: imp-nullRouter#
Configuration Examples for MPLS LDP Inbound Label Binding Filtering
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 terminalRouter(config)# access-list 1 permit 10.63.0.0 0.63.255.255Router(config)# mpls ldp neighbor 10.110.0.10 labels accept 1Router(config)# endIn 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.10tib entry: 10.2.0.0/16, rev 4remote binding: tsr: 10.110.0.10:0, tag: imp-nulltib entry: 10.43.0.0/16, rev 6remote binding: tsr: 10.110.0.10:0, tag: 16tib entry: 10.52.0.0/16, rev 8remote binding: tsr: 10.110.0.10:0, tag: imp-nullAdditional References
Related Documents
Standards
MIBs
MIB MIBs LinkLDP Specification, draft-ietf-mpls-ldp-08.txt
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Feature Information for MPLS LDP Inbound Label Binding Filtering Feature
Table 1 lists the release history for this feature.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 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.
Glossary
carrier supporting carrier—A situation where one service provider allows another service provider to use a segment of its backbone network. The service provider that provides the segment of the backbone network to the other provider is called the backbone carrier. The service provider that uses the segment of the backbone network is called the customer carrier.
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.
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.

