FRR allows to change the way of allocate labels on l3vpn bgp updates , allows to create labels by next-hop or unique per vrf:
Description
Description
Details
Details
- Difficulty level
- Unknown (require assessment)
- Version
- VyOS 1.4-rolling-202308220020
- Why the issue appeared?
- Will be filled on close
- Is it a breaking change?
- Perfectly compatible
- Issue type
- Feature (new functionality)
Event Timeline
Comment Actions
In PR 2152:
As pointed out in the slack, isnt the "nexhop" misspelled?
Should be "nexthop".
Ref:
Comment Actions
I've tested our last rolling-realase , it's working as expected :
set vrf name customer protocols bgp address-family ipv4-unicast export vpn set vrf name customer protocols bgp address-family ipv4-unicast import vpn set vrf name customer protocols bgp address-family ipv4-unicast label vpn allocation-mode per-nexthop set vrf name customer protocols bgp address-family ipv4-unicast label vpn export 'auto' set vrf name customer protocols bgp address-family ipv4-unicast network 10.180.2.0/24 set vrf name customer protocols bgp address-family ipv4-unicast rd vpn export '1:2' set vrf name customer protocols bgp address-family ipv4-unicast redistribute connected
label allocation per-nexthop :
vyos@cust-pe1:~$ show mpls table Inbound Label Type Nexthop Outbound Label ------------------------------------------------- 16 LDP 10.180.3.3 implicit-null 80 BGP customer - 81 BGP 10.180.2.0 -