MPLS LDP Label Filtering Example

This topic is to discuss the following lesson:

For r1 why is 3.3.3.3 untagged?
Similar for r3 why is 1.1.1.1 untagged?

1 Like

That’s what this tutorial is about…filtering tags so not all prefixes get a tag. R2 only sends a tag for 2.2.2.2 /32 to R1 and R3, not for 1.1.1.1/32 or 3.3.3.3/32.

My bad. Just realized that r2 is between r1 and r3

Rene,

Great lesson as usual. However, I have question loop backs which are not label it means they can not be reached and can not be in the routing table?

 

Thanks

 

Hamoood

Hi Hamood,

If there is no label for a prefix then we can still reach it through normal routing with the routing table, the only difference is that it won’t be label switched.

Rene

Good.! I had the same question what cla had. Thanks for answering Rene.!!

why i am seeing TDP instead of LDP.

R1#show mpls ldp neighbor
    Peer TDP Ident: 22.22.22.22:0; Local TDP Ident 11.11.11.11:0
        TCP connection: 22.22.22.22.11014 - 11.11.11.11.711
        State: Oper; PIEs sent/rcvd: 5/5; Downstream
        Up time: 00:01:01
        TDP discovery sources:
          FastEthernet0/0, Src IP addr: 192.168.12.2
        Addresses bound to peer TDP Ident:
          192.168.12.2    2.2.2.2         22.22.22.22     192.168.23.2
R1#
R1#

TDP is the old Cisco equivalent protocol for LDP. LDP is an IETF standard. On older IOS versions, TDP is the default. Nowadays LDP is the default. There is a command to change the protocol:

R1(config)#mpls label protocol ?
  ldp  Use LDP (default)
  tdp  Use TDP
1 Like

Thank you so much Rene…

Hi Rene,

I am little bit confused that where we can use the label filtering in Production network .I am looking for scenario where we deploy it . Thx

br//zaman

Hi Zaman,

Think of an MPLS VPN network where we have PE and CE routers. The PE routers only require an LSP (Label Switched Path) between their loopback interfaces and the /32 IP address that is configured on these loopback interfaces. These are the IP addresses that are used for the next hops in BGP.

By default, LDP creates and advertises a label for each and every prefix that is learned. This increases memory usage but also the number of advertisements between peers. If you only advertise labels for the LSPs that you need, you reduce convergence time and memory usage.

hi

R3(config)#access-list 1 permit 3.3.3.3 0.0.0.0
R3(config)#no mpls ldp advertise-labels
R3(config)#mpls ldp advertise-labels for 1

(mpls ldp advertise-labels for ) is a command ok but ( 1) what for i dont understand

Hello Bahri

The mpls ldp advertise-labels for 1 command is used to control which labels are advertised to which LDP neighbors. The “1” at the end of the command indicates that it is the access list “1” which is configured above that will be used to filter the labels such that labels will be generated only for loopback 0. On R3, 3.3.3.3 is the IP address of loopback 0.

I hope this has been helpful!

Laz

Hello,

I can see that “tag / pop tag” is used in the output. In the previous lesson “label / pop label” was used. Is there any difference?

Many thanks,
Stefanita

Hello Staut

When speaking about MPLS, the term label and tag may be used interchangeably. The term label is the officially correct one, but keep in mind that in the context of MPLS, the term tag may be used as well.

I hope this has been helpful!

laz

1 Like

Hello Rene,
i still confused, where is the filter ? i mean i can see you filtered out all the prefixes not some of them, i think R3 should advertise 3.3.3.3 and filter out 33.33.33.33 but what really see it’s filter out both of them and R1,R2 the same problem.
thanks to demonstrate.

Hello Ahmed

When the filtering mechanism is enabled on each router, it is applied for all networks whether those networks exist on the local router or are received and transmitted by intervening routers. What this means is that R2 will see 1.1.1.1 and 3.3.3.3 labelled while 11.11.11.11 and 33.33.33.33 will not have labels, as expected.

Similarly, R1 will see that 2.2.2.2 is labelled while 22.22.22.22 will not have labels, again as expected. However, because R3 sends its information to R1 via R2, the mpls ldp advertise-labels for 1 command applied to R2 will also filter out those routes delivered from R3. So since both 3.3.3.3 and 33.33.33.33 are filtered out using R2’s filtering mechanism, these arrive at R1 untagged.

A similar situation occurs for routes that are advertised from R1 to R3 which affects how they appear in R3.

I hope this has been helpful!

Laz