Cisco IOS - How to Configure VRF-Lite
What is VRF-Lite?
VRF is a feature that allows you to create separate instances of the routing table. In turn allowing you to segregate and isolate different network types. When VRFs are used without MPLS it is classed as VRF-lite. The configuration for VRF-lite doesn’t need the route-target and can be done by static or dynamic routing under its VRF instance. 
This tutorial will be based on the following topology (Figure 1):
- 2 x VRFs will be configured on router R1 - Green/Red.
- 2 x networks (188.8.131.52/184.108.40.206) will be configured on router R1, one placed into each of the VRFs.
- eBGP peerings will then be established to each neighbor (Red/Green).
- eBGP will advertise the corresponding VRF network to its peer:
- Green VRF - 220.127.116.11
- Red VRF - 18.104.22.168.
Figure 1 - Topology.
First all we configure the 2 VRFs. Each VRF is assigned a Route Distinguisher.
ip vrf GREEN rd 65001:100 ip vrf RED rd 65001:200
Next, we configure our interfaces. Each loopback and the interface connecting R1 to its neighbor is placed into a separate VRF (Figure 1).
interface Loopback1 ip vrf forwarding GREEN ip address 22.214.171.124 255.255.255.0 ! interface Loopback2 ip vrf forwarding RED ip address 126.96.36.199 255.255.255.0 interface GigabitEthernet0/1 description to GREEN ip vrf forwarding GREEN ip address 10.0.0.10 255.255.255.252 ! interface GigabitEthernet0/2 description to RED ip vrf forwarding RED ip address 10.0.0.5 255.255.255.252
BGP is configured. We use the ipv4 address families to specify our VRFs and redistribute our connected interfaces into BGP.
NOTE We use the IPv4 address family rather then VPNv4. VPNv4 routes are nothing more than IPv4 routes with an additional 64 byte Route Distinguisher header assigned.
router bgp 65001 bgp router-id 188.8.131.52 bgp log-neighbor-changes address-family ipv4 vrf GREEN redistribute connected neighbor 10.0.0.9 remote-as 65002 neighbor 10.0.0.9 activate exit-address-family address-family ipv4 vrf RED redistribute connected neighbor 10.0.0.6 remote-as 65003 neighbor 10.0.0.6 activate exit-address-family
The configuration for Green is a simple eBGP peering. Like so,
router bgp 65002 bgp router-id 184.108.40.206 bgp log-neighbor-changes redistribute connected neighbor 10.0.0.10 remote-as 65001
We then, again configure on Red another eBGP peering.
router bgp 65003 bgp router-id 220.127.116.11 bgp log-neighbor-changes redistribute connected neighbor 10.0.0.5 remote-as 65001
First, we will check that the BGP adjacencies have correctly formed on R1, Green, and Red. From the output, we can see BGP has successfully established adjacency with its neighbor, and that we have received prefixes.
R1#show ip bgp vpnv4 vrf RED summary ! Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.0.0.6 4 65003 36 36 8 0 0 00:28:46 2 R1#show ip bgp vpnv4 vrf GREEN summary ! Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.0.0.9 4 65002 51 51 8 0 0 00:42:07 2
GREEN#show ip bgp sum ! Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.0.0.10 4 65001 58 59 7 0 0 00:49:01 2
RED#show ip bgp sum ! Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.0.0.5 4 65001 46 46 5 0 0 00:38:11 2
Finally, we check the routing table on, both the Green and the Red router, in order to confirm we have learned the routes advertised from the corresponding VRF on R1.
GREEN#show ip route ! 18.104.22.168/32 is subnetted, 1 subnets C 22.214.171.124 is directly connected, Loopback0 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks C 10.0.0.8/30 is directly connected, GigabitEthernet0/1 L 10.0.0.9/32 is directly connected, GigabitEthernet0/1 126.96.36.199/24 is subnetted, 1 subnets B 188.8.131.52 [20/0] via 10.0.0.10, 00:49:06
RED#show ip route ! 184.108.40.206/32 is subnetted, 1 subnets C 220.127.116.11 is directly connected, Loopback0 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks C 10.0.0.4/30 is directly connected, GigabitEthernet0/1 L 10.0.0.6/32 is directly connected, GigabitEthernet0/1 B 18.104.22.168/24 [20/0] via 10.0.0.5, 00:38:05
Success, as we can see the advertised routes from R1’s VRF on each router.