All IOS-based routers offer a command line interface that allows engineers to interact with Cisco devices. BackgroundĮxperienced Cisco route engineers have been working for many years with Cisco’s IOS. This article provides with a few insights that I consider you should know if you are a post-sales engineer and new to the Cisco SD-WAN technology. If you are trying something new to discover new trends and technologies or maybe because you are an implementation engineer and a Cisco SD-WAN project landed on your desk, you may want to know a few things before your project kicks off. Many of us have been Cisco engineers for so many years and worked on the command line every time we work on an IOS devices. In this post, I will summarize 7 items that I consider important and think you will need to know if you have not had exposure to Cisco SD-WAN. If you are a seasoned Cisco engineer with knowledge of and experience with Dynamic Multipoint VPNs and/or iWAN, and you want to get started with Cisco SD-WAN with cEdges (IOS-based SD-WAN routers), this paper may be for you. Written by Rio Zavarace, Principal Consulting Engineer, Aspire Technology Partners 2018.7 Tips You Should Know Prior to Implementing Cisco SD-WAN cEdges "VRF vs VRF Lite | IP With Ease | IP With Ease." 28 Dec. Success, as we can see the advertised router from R1’s VRF on each router. GREEN#show ip routeĬ 2.2.2.2 is directly connected, Loopback0ġ0.0.0.0/8 is variably subnetted, 2 subnets, 2 masksĬ 10.0.0.8/30 is directly connected, GigabitEthernet0/1 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcdįinally, we check the routing table on, both the Green and the Red router, in order to confirm we have learnt the routes advertised from the corresponding VRF on R1. From the output, we can see BGP has successfully established adjacency with its neighbour, and that prefixes have been received. router bgp 65003įirst, we will check that the BGP adjacencies have correctly formed on R1, Green and Red. We then configure another eBGP peering on Red. The configuration for Green, is a simple eBGP peering. Therefore in our example the RD is only locally significant to R1, hence vpnv4 being used within the R1 show commands. Note : The IPv4 address-family exchanges normal IPv4 unicast routes, without any route distinguisher (RD). We use the IPv4 address families to specify our VRFs and redistribute our connected interfaces into BGP. Each loopback and the interface connecting R1 to its neighbor is placed into their corresponding VRF.
Each VRF is assigned a Route Distinguisher. Configuration Router - R1 VRFsįirst of all we configure the 2 VRFs. eBGP will advertise the corresponding VRF network to its peer:įigure 1 - Topology.eBGP peerings will then be established to each of the neighbours (Red/Green).2 x networks (100.1.1.0 and 200.1.1.0) will be configured on router R1, one placed into each of the VRFs.2 x VRFs will be configured on router R1 - Green/Red.This tutorial will be based on the following topology (Figure 1): VRF-lite configuration doesn’t need the route-target and can be done by static or dynamic routing under its VRF instance.
When VRFs are used without MPLS it is classed as VRF-lite.
In turn allowing you to segregate and isolate different network types. VRF is a feature that allows you to create separate instances of the routing table.