Filter
Top Products
Understanding VRF-lite
Page 10 | Configure VRF-lite
VRF-lite features in AW+
Here is a summary of the features provided by the AW+ VRF-lite implementation:
Multiple independent routing table instances may co-exist within the same device. The
same or overlapping IP addresses can be present in different route table instances without
conflicting. All routing table instances remain securely isolated from those existing in other
routing tables.
By default, no communication occurs between VRF instances, facilitating multiple secure
routing domains within the same VRF aware device.
However, inter-VRF communication between routing domains is possible by using either
static inter-VRF routes and/or dynamic filtered route leakage via BGP and its associated
route maps.
A single device configuration file simplifies management by providing the ability to create,
manage, and monitor all VRF instances.
Detailed diagnostic and debugging information is available.
Ability to view routing table information per VRF.
All appropriate VRF related information and error messages can be viewed in the
system wide log.
Separate instances of routing protocols can be mapped to VRF instances so that
distribution of route information can be performed on a per VRF domain basis. This
enables route information to be distributed securely within each VRF routing domain.
For example:
VRF1 = OSPF routing instance1
VRF2 = OSPF routing instance2
All Layer 3 interfaces and associated switch ports remain in the default global VRF domain
until associated with a specific VRF instance.
VRF is supported in HW and SW (including Inter-VRF communications).
The default global VRF domain always exists and cannot be removed. Initially during
startup, every VLAN belongs to the default global VRF domain. Also, when a VLAN is
removed from a VRF, it is automatically returned to the default global VRF domain. Only
one default global VRF domain exists in each physical device.
Static and dynamic routes can be leaked from a VRF instance to the global default VRF.
Selected routes within a VRF instance can be dynamically leaked to other VRF routing
domains. This applies both to routes that have been statically configured, and to routes
that have been learnt into a VRF instance on the device by routing protocol exchanges
with external peer routers.
When a VRF instance has received routes leaked from other VRF instances, that instance
can advertise those routes to external peer routers connected to interfaces in that VRF
instance, via the routing protocol operating within the VRF instance.