Rendo - Please open an issue on github with this information. donald On Fri, Apr 27, 2018 at 9:30 AM, rendo <rendo.aw@gmail.com> wrote:
Hi,
I am not sure if this is specific to cumulus or FRR in general, It seems the route-target config for evpn (maybe for other family too) has some magic if the 2 byte number has more than 3 digit.
I am adding a new vni 12345 with RT 64000:12345. The RT simply disappear
r1(config-router-af)# vni 12345 r1(config-router-af-vni)# rd 172.16.10.10:12345 r1(config-router-af-vni)# route-target both 64000:12345 r1(config-router-af-vni)# r1(config-router-af-vni)# do sh run Building configuration...
...
router bgp 64000 address-family l2vpn evpn neighbor 10.7.0.3 activate neighbor 10.7.0.22 activate vni 12345 rd 172.16.10.10:12345 exit-vni vni 31100 rd 172.16.20.20:31100 route-target import 64000:31100 route-target export 64000:31100 exit-vni ...
now i add "shorter" RT before putting the intended RT, both RT shows up
r1(config-router-af-vni)# route-target both 64000:12 r1(config-router-af-vni)# route-target both 64000:12345 r1(config-router-af-vni)# do sh run ... vni 12345 rd 172.16.10.10:12345 route-target import 64000:12 route-target import 64000:12345 route-target export 64000:12 route-target export 64000:12345 exit-vni ...
and if i delete the dummy RT, the intended RT still there
r1(config-router-af-vni)# no route-target export 64000:12 r1(config-router-af-vni)# no route-target import 64000:12 r1(config-router-af-vni)# r1(config-router-af-vni)# do sh run ... vni 12345 rd 172.16.10.10:12345 route-target import 64000:12345 route-target export 64000:12345 exit-vni ....
could someone please take a look?
note: cumulus version is 3.5.3, FRR version is 3.2+cl3u4
thanks.
rendo
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog