IOS XE - Category - Fryguy's Bloghttps://hugo.fryguy.net/categories/ios-xe/IOS XE - Category - Fryguy's BlogHugo -- gohugo.ioenFri, 27 Dec 2013 14:00:40 +0000Cisco CSR1000v For Home Labshttps://hugo.fryguy.net/2013/12/27/cisco-csr1000v-for-home-labs/Fri, 27 Dec 2013 14:00:40 +0000Fryguyhttps://hugo.fryguy.net/2013/12/27/cisco-csr1000v-for-home-labs/

I have been using the Cisco CSR1000V for my home lab setup for a little bit now.  There have been some questions on how to set this up for a home lab and I figured I would cover how I am using it.
For this post, here is what we are going to build –  a three (3) node CSR1000V network and three (3) vSwitch Networks to connect the CSR1000Vs together.  We will also configure the CSR1000V to have connectivity back to the “home production” network so that we can SSH/Telnet to these routers when we are labbing.

Obtaining the CSR1000V Router Software

To obtain the Cisco CSR1000V you need to download it from Cisco at this LINK and click on the Download software as seen circled below

]]>VASI – VRF Aware Service Infrastructure Interfaces and Global Route Leakinghttps://hugo.fryguy.net/2013/08/28/vasi-vrf-aware-service-infrastructure-interfaces-and-global-route-leaking/Wed, 28 Aug 2013 12:15:34 +0000Fryguyhttps://hugo.fryguy.net/2013/08/28/vasi-vrf-aware-service-infrastructure-interfaces-and-global-route-leaking/Cisco has defined a VASI interface as: VASI is implemented using virtual interfaces that provide the framework necessary to configure a firewall and NAT between VRF instances. Each interface pair is associated with two different VRF instances. The two virtual interfaces, called vasileft and vasiright, in a pair are logically wired back-to-back and are completely symmetrical. Each interface has an index. The association of the pairing is done automatically based on the two interface indexes such that vasileft automatically gets paired to vasiright. So you could look at a VASI interface as like a back-to-back connection between VRFs –  call it a virtual cable of sort.  You can also see that the traditional use of a VASI interface is to connect two VRFs, on the same router, together so they can route and NAT between each other.  But what I am saying about Global Route Leaking? Well, recently I had a problem where a client wanted to leak routes, dynamically, from a VRF to the Global table on an ASR1000 with an RP1 installed.  We could easily have done it via a physical cable, but I knew their had to be a better way.  I did some digging on the VASI interface and possible configurations and came across this –  added in IOS XE 3.10S code is the ability to actually BGP peer over the VASI interfaces to exchange routes.
You may click on the image below to view the PDF on this.]]>