BIRD - Config Support for RFC 3107 - Carrying Label Information in BGP

[Thiruvazhiyan Lakshmanan]

Hi Ondrej,
Thanks for your reply. The link which is provided in your emails details about the static MPLS route entry to the MPLS route table. When we have our VM with the latest kernel, whether BIRD can program the incoming 3107 routes to the MPLS Kernel table automatically, or do we need to make static entries in the kernel table?

Regards, 
Thiruvazhiyan L


-----Original Message-----
From: Bird-users [mailto:bird-users-bounces at network.cz] On Behalf Of Ondrej Zajicek
Sent: Friday, June 8, 2018 3:26 PM
To: Thiruvazhiyan Lakshmanan
Cc: bird-users at network.cz
Subject: Re: BIRD - Config Support for RFC 3107 - Carrying Label Information in BGP

On Fri, Jun 08, 2018 at 04:03:41PM +0000, Thiruvazhiyan Lakshmanan wrote:
> Hi Ondrej,
> Thanks for your reply. What is the recommended linux kernel verison for mpls if BIRD acts as a PE. 
> 
> We have VM with Red Hat Enterprise Linux Server 7.3 (Maipo)
> Kernel 3.10.0-693.2.2.el7.x86_64 on an x86_64
> 
> And Bird 2.0.1 version, but it is not working. Can you please confirm whether the environment we have is supporting mpls. If not, what is the recommended kernel version.

Hi

I think that 2.0.1 is OK, i don't there is any related bugfix in 2.0.2.

But your kernel is probably too old, MPLS forwarding is rather recent feature.

You should check that you can doo MPLS routes with basic iproute2 commands
(so you have recent kernel and iproute2 tools):

https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_questions_31926342_iproute2-2Dcommands-2Dfor-2Dmpls-2Dconfiguration&d=DwIBAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=Hr9lSHBFHFernxnRV47c1g&m=3soah1ahphq6LNdfZRHIw9ncGMuKnewxMW8YuVF1E38&s=nFYPMHSQa0F5NPaXsEXtq-TmsJ1WR3ChXM7rziJM84I&e=

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
============================================================================================================================

Disclaimer:  This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra.

============================================================================================================================