Hello @KestutisGrigas2465 ,
for routing between VRFs the most elegant and powerful solution is to use route-targets as explained in the article linked by the other colleague
ip vrf Employee
description Employee and students
!
ip vrf Servers
description Servers
!
you need to add a RD route distinguisher and route-targets and use MP BGP defining the address family for each VRF .
RD values must be unique per VRF per node.
Route-targets can be imported and exported multiple values ( they are extended communities)
if VRF A exports routes with at least one route-target associated to it that VRF B imports the routes will appear in VRF B routing table , the same is valid in the opposite direction.
For leaking routes between a VRF and the global routing table the things are different : you cannot use route targets because route in Global routing table have no route targets associated to them by definition.
You can create a link between one port in GRT and one port in VRF and using a common IP subnet, and you can use static routes to create bidirectional connectivity.
Routes in global routing table have the form
ip route ....
statci routes in VRF
ip route vrf <vrf-name>.
At the end of the static route you can add the interface name in addition to the next-hop.
This is the oldest approach with a LAN cable between two ports.
Some improvements have been introduced so that for example static routes in VRF can add the keyword global to say the next-hop is to be searched in global routing table.
Hope to help
Giuseppe
