[FROG] import vrf works in running config, but not after write mem and frr restart

[Rainbow Dash]

> On 23. Dec 2020, at 21:13, Don Slice <dslice at cumulusnetworks.com> wrote:
> 
> Do you need to use different ASNs for the different VRFs?  If not, change to the same ASN and see if you have better luck. There is work under way to support different ASNs for VRFs and default instance but not yet completed. 

At this point I‘m in the testing phase. I‘ve build a demo setup with Cumulus VX and some Linux VMs running frr. We plan to go live on real hardware In Q2/Q3 2021. So there is some time left to figure out.

We have to connect to two tenants. Each party expects us to use a private ASN in a certain range (both different).
My (maybe naive) approach was to create a VRF for each tenant with the required ASNs and import all routes from both VRFs into my default VRF and vice versa.

I discovered that frr does read the configuration correctly when first defining all the router bgp blocks with all the settings but without the imports and repeat the router bgp blocks at the bottom with only the import vrf commands.
We doing this, I cannot use vtysh to modify the config, because frr combines the settings, but when only modifying the frr.conf externally this seems to work.


Cheers,
Sascha 




> 
> Don
> 
>> On Wed, Dec 23, 2020 at 2:19 PM 0xbabaf00l <0xbabaf00l at gmail.com> wrote:
>> Hi list,
>> 
>> I'm trying to import routes from one VRF into my default VRF.
>> 
>> This is my sample config:
>> 
>> debian# show running-config
>> Building configuration...
>> 
>> Current configuration:
>> !
>> frr version 7.4
>> frr defaults traditional
>> hostname debian
>> log syslog informational
>> no ip forwarding
>> no ipv6 forwarding
>> service integrated-vtysh-config
>> !
>> router bgp 11111
>>  !
>>  address-family ipv4 unicast
>>   network 1.1.1.0/24
>>  exit-address-family
>> !
>> router bgp 22222 vrf red
>>  !
>>  address-family ipv4 unicast
>>   network 2.2.2.0/24
>>  exit-address-family
>> !
>> line vty
>> !
>> end
>> 
>> 
>> Now I add the import:
>> 
>> debian# conf t
>> debian(config)# router bgp 11111
>> debian(config-router)# address-family ipv4 unicast
>> debian(config-router-af)# import vrf red
>> debian(config-router-af)# end
>> 
>> 
>> Everything works fine. ‘show running-configuration’ shows the correct config.
>> 
>> Then I save the config and restart frr:
>> 
>> debian# write mem
>> Note: this version of vtysh never writes vtysh.conf
>> Building Configuration...
>> Integrated configuration saved to /etc/frr/frr.conf
>> [OK]
>> debian# exit
>> root at debian:~# systemctl restart frr
>> root at debian:~# vtysh
>> 
>> Hello, this is FRRouting (version 7.4).
>> Copyright 1996-2005 Kunihiro Ishiguro, et al.
>> 
>> debian# sh ru
>> Building configuration...
>> 
>> Current configuration:
>> !
>> frr version 7.4
>> frr defaults traditional
>> hostname debian
>> log syslog informational
>> no ip forwarding
>> no ipv6 forwarding
>> service integrated-vtysh-config
>> !
>> router bgp 11111
>>  !
>>  address-family ipv4 unicast
>>   network 1.1.1.0/24
>>   import vrf red
>>  exit-address-family
>> !
>> router bgp 11111 vrf red
>> !
>> line vty
>> !
>> end
>> 
>> 
>> Why is the router bgp 22222 vrf red block now missing?
>> 
>> As I said, this configuration worked fine until I saved it and restarted frr.
>> 
>> 
>> Cheers,
>> Sascha
>> 
>> _______________________________________________
>> frog mailing list
>> frog at lists.frrouting.org
>> https://lists.frrouting.org/listinfo/frog
> -- 
> Don Slice
> Cumulus Networks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/frog/attachments/20201226/3861a204/attachment.htm>