Filter
Top Products
awplus(config)#arp ?
A.B.C.D IP address of the ARP entry
log Arp log
vrf VRF instance
awplus(config)#arp vrf <name> ?
A.B.C.D IP address of the ARP entry
Confi
gure VRF-lite | Page 7
Understanding VRF-lite
When a Layer 3 interface is moved to a VRF instance from the default global VRF domain, or
when a Layer 3 interface is moved from one VRF instance to another via command, the
interface name and id (ifindex) are never changed as a result of the interface movement.
However IP configuration on the interface in the previous VRF is unset (removed) before
moving the interface to a new VRF.
ARP entries associated with the Layer 3 interface are cleared when the interface is moved
from one VRF instance to another. In addition (static and dynamic) ARP entries are VRF
aware, as the same IP address can be used in other VRF instances.
Adding a VRF-aware static ARP
Route management with VRF
Each VRF instance maintains its own IPv4 routing table independent from the routing table
of the global VRF domain or other VRFs.
Routing entries can be added statically by user command or dynamically by a routing
protocol module such as BGP, OSPF, or RIP within the VRF instance. Use of a dynamic
routing protocol allows for each VRF network to maintain a consistent routing table across
all the devices within the VRF network.
The way that each routing is able to define a separate instance of itself on multiple VRF
instances varies from protocol to protocol:
For BGP, one BGP routing instance will be running for an Autonomous System in the
global VRF domain and individual BGP routing tables will be managed per VRF by using
the address-family feature. One address-family is created for each VRF instance.
For OSPF, one OSPF routing instance is configurable per VRF, and one OSPF instance
is configurable within the global VRF domain.
For RIP, one RIP routing instance will be running in the default global VRF domain and
individual RIP routing tables will be managed per VRF by using the address-family
feature. One address-family is created for each VRF instance.
Note: The command show ip route displays the routes associated with each VRF instance.