Filter
Top Products
Configure VRF-lite | Page 45
Configuring a complex inter-VRF solution
VRF communication plan
VRF shared can access all VRFs red, green, blue and orange (excluding VRF overlap).
VRFs red, green, blue, and orange are only able to access VRF shared. They cannot access
each other in this example.
VRF overlap remains completely isolated from all other VRFs, and it has a connected route
to subnet 192.168.10.0/24, which is also configured in VRF red. No routes are exported
from or imported to VRF overlap, ensuring there is no IP address range overlap conflict
when performing inter-VRF communication.
VRF red can access the Internet, and VRF shared subnets, 192.168.100.0/24, 192.168.43.0/
24, but VRF red cannot access VRF shared subnets 192.168.44.0/24, 192.168.45.0/24.
VRF red has a connected route to subnet 192.168.10.0/24, which is also configured in VRF
overlap. This connected route in VRF red is leaked to other VRFs.
VRF green can access the Internet, and VRF shared subnets, 192.168.100.0/24,
192.168.44.0/24, but VRF green cannot access VRF shared subnets 192.168.43.0/24,
192.168.45.0/24.
VRF green has a connected route to subnet 192.168.20.0/24, which overlaps a static route
configured in VRF orange. This connected route in VRF green is leaked to other VRFs.
VRF blue can access the Internet, and VRF shared subnets, 192.168.100.0/24,
192.168.45.0/24, but VRF blue cannot access VRF shared subnets 192.168.43.0/24,
192.168.44.0/24.
VRF orange can access the Internet, and can also access all VRF shared subnets,
192.168.100.0/24, 192.168.43.0/24,192.168.44.0/24, 192.168.45.0/24.
VRF orange has static route to subnet 192.168.20.0/24, which overlaps a connected route
configured in VRF green. Therefore this subnet is not leaked from VRF orange to other
VRF instances, ensuring there is no IP address range overlap conflict when performing
inter-VRF communication.