![ccna network visualizer export configs ccna network visualizer export configs](https://image.slidesharecdn.com/234821765-ccna-virtual-lab-160816193514/95/234821765-ccnavirtuallab-35-638.jpg)
Back at the headquarters we have our VRF policy set to import both the Red and Green routes. When the Branch 1 PE peer receives the routes it sees that it’s VRF policy is stating to export its routes as the color Red as well as import any routes that are colored Blue. These routes are passed around to the other PE routers. HQ CE peers with its PE router which has a VRF policy stating to export its routes as the color Blue. Lets follow a case from the HQ to Branch 1. At this point we can write a policy of which routers should be allowed into the individual CE routes using the VRF Route Target import. The VRF configuration on the PE routers is what indicates the Router Target identifier to export. The CE routers in this example our peering via eBGP with the PE routers inside of a VRF. This exporting is done by the PE routers connecting to the CE routers. Routes exported from Branch 2 will use 20:8 which we will call the “Green Routes” Routes exported from Branch 1 will use 10:8 which we will call the “Red Router” Routes exported from the headquarters use 30:8 which we will call the “Blue Routes” I am going to correlate their indicators with colors to make the example easier to visualize. To clarify exactly what they are used for I have used three different Router Targets. Many examples and videos show these as the same (which is a perfectly valid configuration) often times matching the RD. There are two route targets we define in our VRF policy. Now that we are clear on the use of the RD we can move onto the Route Targets.
![ccna network visualizer export configs ccna network visualizer export configs](https://www.cisco.com/c/dam/en/us/td/i/400001-500000/410001-420000/411001-412000/411649.jpg)
#Ccna network visualizer export configs install
This means if another vrf with a different RD of 4242:42 could also install 10.20.30.40 in the providers BGP table as 4242:42:10.20.30.40. For example, my RD of 65000:8 indicates any routers in the BGP table from my customer vrf would indicate a prefix of 10.20.30.40 as 65000:8:10.20.30.40. The purpose of the RD so to add an additional label to prefixes so overlaps can be inserted in the BGP table and shared amongst the various PE routers. To make this concept easier to understand we first need to know that the RD does not dictate what routes a route will import or export into it’s PE-CE routing process.