Wednesday, November 5, 2014

Virtual Routing and Forwarding

So, I'm reading, among other things, Network Warrior by Gary A. Donahue.  In the chapter I'm on now, he briefly talks about VRFs, or Virtual Routing and Forwarding.  This was NOT on the CCNA exam.

My very basic understanding of VRFs is that they are self-contained routing tables within the same router.  So, this ties in with all of the virtualization that is going on now.  According to Donahue, you can have multiple VRFs within a single Virtual Device Context (VDC).  This sounds great, on the surface, but like many things in my educational life, I don't understand WHY I would want that.  I'm sure some network pros out there might read this and scoff, but I am just getting started, so give me a break here.

OK, so when we don't understand something, we go and find out for ourselves.  At least, that's what I feel we should do.  After doing just a bit of reading, the benefit of using a VRF is mainly that you can have overlapping IP addresses with no conflict.  So, one routing table (VRF) instance could have 10.1.23.3 in it, and another routing table (VRF) could have the SAME IP address, with no conflict.  You might want to organize things this way in order to keep customer traffic separate.

The way I would do this now, because I am a recent CCNA, would be by setting up VLANs and ACLs.  This is a great way to go in a lot of instances, but not all.  Hence the utility of VRFs.

I am not yet at a point where I am ready to use this technology, but I think that I am beginning to understand it now.