Hi Renato,

I already set and verified those parameters.

My topology is





PE1 Configuration:

root@frr:/usr/local/etc/quagga# modprobe mpls-router mpls-iptunnel
root@frr:/usr/local/etc/quagga# sysctl -p /etc/sysctl.d/90-routing-sysctl.conf
net.ipv4.conf.all.forwarding = 1
net.ipv6.conf.all.forwarding = 1
net.mpls.conf.ens3.input = 1
net.mpls.conf.ens4.input = 1
net.mpls.conf.ens9.input = 1
net.mpls.conf.ens10.input = 1
net.mpls.platform_labels = 100000
root@frr:/usr/local/etc/quagga# ip route
default via 192.168.13.1 dev ens3 proto static
192.168.13.0/24 dev ens3 proto kernel scope link src 192.168.13.42
192.168.123.0/24  encap mpls  100 via 192.168.200.3 dev ens9
192.168.200.0/24 dev ens9 proto kernel scope link src 192.168.200.2
root@frr:/usr/local/etc/quagga#

PE2 Configuration:

root@frr:~/frr-4.0-vPE# modprobe mpls-router mpls-iptunnel
root@frr:~/frr-4.0-vPE# sysctl -p /etc/sysctl.d/90-routing-sysctl.conf
net.ipv4.conf.all.forwarding = 1
net.ipv6.conf.all.forwarding = 1
net.mpls.conf.ens3.input = 1
net.mpls.conf.ens4.input = 1
net.mpls.conf.ens9.input = 1
net.mpls.conf.ens10.input = 1
net.mpls.platform_labels = 100000
root@frr:~/frr-4.0-vPE#root@frr:~/frr-4.0-vPE# ip route
default via 192.168.13.1 dev ens3 proto static
192.168.13.0/24 dev ens3 proto kernel scope link src 192.168.13.43
192.168.100.0/24 dev ens4 proto kernel scope link src 192.168.100.3
192.168.111.0/24 dev ens10 proto kernel scope link src 192.168.111.3
192.168.200.0/24 dev ens9 proto kernel scope link src 192.168.200.3
root@frr:~/frr-4.0-vPE# ip route
default via 192.168.13.1 dev ens3 proto static
192.168.13.0/24 dev ens3 proto kernel scope link src 192.168.13.43
192.168.111.0/24 dev ens10 proto kernel scope link src 192.168.111.3
192.168.200.0/24 dev ens9 proto kernel scope link src 192.168.200.3
root@frr:~/frr-4.0-vPE# ip -f mpls route show
100 dev ens10
root@frr:~/frr-4.0-vPE#

I have a route in 

Did you enable MPLS processing on your interfaces?

Please check this link:
https://github.com/FRRouting/frr/blob/frr-5.0.1/doc/developer/building-frr-on-ubuntu1804.rst#enable-mpls-forwarding-with-linux-kernel--45

Cheers,
Renato.

On Mon, Jul 16, 2018 at 10:45 AM, Vijayalakshmi
<vijayalakshmi.marudhanayagam@veryxtech.com> wrote:

Hi Kishore,

Thanks for your reply.

I tried the same with Linux MPLS via iproute2 configuration. Still the
behavior is same.
So it is clear that the issue is not with FRR.

Let me fix the issue in my Linux kernel and get back to you if I need any
support.

Regards,
Vijayalakshmi

On 7/13/2018 9:45 PM, Kishore Aramalla wrote:

Vijayalakshmi, Can you share your configuration.



Best,

Kishore



From: dev <dev-bounces@lists.frrouting.org> On Behalf Of Vijayalakshmi
Sent: Thursday, July 12, 2018 11:49 PM
To: dev@lists.frrouting.org
Subject: [dev] MPLS SWAP and POP configuration issue



Hello,

We are currently working with simulating a PE router in MPLS architecture.
We run zebra and ldp with below configuration
and facing issues in swapping and popping of label in zebra.

In my MPLS table I have the following entries,

zebra_2# show mpls table
 Inbound                            Outbound
   Label     Type          Nexthop     Label
--------  -------  ---------------  --------
      16      LDP    192.168.100.2         3
      17   Static    192.168.100.2        18

But still zebra is not swapping the label and also not forwarding the
received traffic (inbound label 16/17) to the respective nexthop.

Is there any special command to activate mpls configuration ?
Can someone help us in a configuring zebra MPLS to pop label and swap label?

Thanks,
Vijayalakshmi



_______________________________________________
dev mailing list
dev@lists.frrouting.org
https://lists.frrouting.org/listinfo/dev