Hello Radek,
this easy VPN solution document tries to avoid to use BGP
![](https://www.cisco.com/c/dam/en/us/td/i/100001-200000/190001-200000/199001-200000/199932.eps/_jcr_content/renditions/199932.jpg)
Even when using standard L3 VPN and route targets importing a RT for spoke VRF sites, the HUB site is not allowed to export again what it has imported from other VRFs. IT can export with a different RT value only "local" routes not learned via import process from VPNv4 table.
This is a consistency check that is performed to avoid to have routes re-injection.
>> Under bgp configuration when I tried to use redistribute connected routes from tenants do not import into BGP table.
This is equivalent to the above description you cannot re-export what you have learned from other VRFs.
The replication of routes is safe in single node only (local scope)
You need to create an aggregate route one or more then one that covers the Spoke prefixes and then you can advertise these to some other router via eBGP or via MP BGP.
Hope to help
Giuseppe