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

[Thiruvazhiyan Lakshmanan]

Hi Obdrej,
Thanks for your help, I have couple of questions.
1. Do we have this supported in bird 2.0.1 version or 2.0.2 version?
2. Other question is, I am currently running 2.0.1 version, is it possible to update the version to 2.0.2 version using any update command? Or do I need to uninstall 2.0.1 and reinstall 2.0.2?

Thanks & Regards, 
Thiruvazhiyan L

-----Original Message-----
From: Ondrej Zajicek [mailto:santiago at crfreenet.org] 
Sent: Wednesday, May 23, 2018 3:07 PM
To: LAKSHMANAN, THIRUVAZHIYA; Thiruvazhiyan Lakshmanan
Cc: bird-users at network.cz
Subject: Re: BIRD - Config Support for RFC 3107 - Carrying Label Information in BGP

On Wed, May 23, 2018 at 06:02:30PM +0000, LAKSHMANAN, THIRUVAZHIYA wrote:
> In the BIRD 2.0 user guide, I see the support for RFC 3107 - Carrying
> Label information in BGP. We want to configure a VM with BIRD agent
> working like a PE for adding MPLS labels for IPv4 and IPv6 unicast
> routes. Do we have this configuration supported now, and can I get any
> sample working configuration for this please.

Hi

Unfortunately BIRD support for MPLS is currently limited. Can be used as
a BGP route reflector, or can configure static MPLS routes (with static
labels) and announce them. But no automatic route labeling.

For example, see this config:

https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.labs.nic.cz_labs_bird_blob_int-2Dnew_doc_bird.conf.example2&d=DwIBAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=Hr9lSHBFHFernxnRV47c1g&m=y1skjbkFAdMW-5IndOMkfI5IuDP0a_Bt4-_6t4LINzw&s=cMfQDt7h5gHQayPG5HJOnY9pNYu6RSJjC1mlFKZdVkw&e=
(although static routes there are VPN routes, it is analogous).

-- 
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.

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