Awesome lesson, thank you so much. However, there are a few things that are not clear to me.
First, where exactly would VRF Lite be used? Are there any examples for this?
I can see how VRF could be used in an MPLS deployment, as the ISP may have a lot of customers there with duplicate private IP space. However, when it comes to VRF Lite, in what situations would we want to use it?
VRF is typically employed with MPLS. However, when VRF is used without MPLS, it is called VRF-lite. What are some use cases for VRF lite? Well here is a partial list:
To serve multi-tenancy: If you have a single network infrastructure, you can create VRFs for each tenant within a building to create their own virtual network topology, thus freeing individual tenants within a building to use their own addressing scheme.
Used with EVN: Easy VIrtual Network is a feature that uses VRF-lite to create multiple routing tables within a routing infrastructure.
I recently built a lab with VRF. But I did not understand the purpose of putting a interface and an ip address for the next hop
Ex: ip route 0.0.0.0 0.0.0.0 gi0/0 10.1.2.1
I am use to seeing just the ip address
Ex: ip route 0.0.0.0 0.0.0.0 10.1.2.1
What you are referring to is called a āFully Specified Routeā. Such a route in the routing table includes both the exit interface and the next hop IP address in the entry. You can also have a route that has only the exit interface or a route that has only the next hop IP. Whether a fully specified route or not, all of these are acceptable, however, they function a little bit differently when we perform a routing table lookup.
Thank you for the explanation . i dont see the DN bit in ospf header as well in the LSAs packet. Could you please provide more details on DN and other bits as well.
The Down Bit or the DN bit can be found within the Options section of an LSA found within the payload of an OSPF message. Take a look at this screenshot of a packet capture to see where you can find it:
The DN bit is found in all LSAs as well as in DB description messages, and is used for much the same purpose. You can find out more information about it at this post, which also includes linksā¦
Thatās a great question. Both of these options will implement VRFs, however, the first is the legacy version, while the second is the newer version.
The newer version delivers advanced flexibility because it puts you into the VRF configuration mode. Within that mode you can configure a whole series of parameters. Take a look at this context-sensitive help that shows the available commands within the VRF configuration mode:
R1(config)#vrf definition CUSTOMER1
R1(config-vrf)#?
VPN Routing/Forwarding instance configuration commands:
address-family Enter Address Family command mode
default Set a command to its defaults
description VRF specific description
exit Exit from VRF configuration mode
help Description of the interactive help system
ipv4 VRF IPv4 configuration
no Negate a command or set its defaults
rd Specify Route Distinguisher
route-target Specify Target VPN Extended Communities
vnet Virtual NETworking configuration
vpn Configure VPN ID as specified in rfc2685
R1(config-vrf)#
Can you do the same configuration with both? Yes, however, with vrf definition, you explicitly configure address families (e.g., address-family ipv4 or ipv6) under the VRF configuration mode. This allows simultaneous IPv4/IPv6 support.
The legacy ip vrf command implicitly enables IPv4 and lacks native IPv6 support without additional configuration.
So both will work, but the latter is the newer implementation method. As with most of these features, eventually, the ip vrf command will be deprecated in favor of the newer method.
Hi Rene, Thanks for explaining this topic with such simplicity and ease. I have one question: Are VRFs used only between CE and PE or are there any scenarios in which we can run them in our local networks as well for better segregation? If yes, can you please explain such scenario(s)?
VRFs are not limited to CE-PE architectures for MPLS in service provider networks. VRFs allow you to logically separate routing domains, which can be useful in a wide variety of scenarios. These include implementation in local enterprise networks for traffic segregation, security, and IP address overlap resolution. Specific scenarios include departmental network isolation, multi-tenant environments, and guest network segmentation.