# MPLS VPN VRF Import Map

**URL:** https://forum.networklessons.com/t/mpls-vpn-vrf-import-map/2405
**Category:** Lessons Discussion
**Created:** [November 15, 2017, 4:07pm UTC](https://forum.networklessons.com/t/mpls-vpn-vrf-import-map/2405 "2017-11-15T16:07:25Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![ReneMolenaar](https://cdn-forum.networklessons.com/user_avatar/forum.networklessons.com/renemolenaar/32/488_2.png) [@ReneMolenaar](https://forum.networklessons.com/u/ReneMolenaar)
#### Post date: [January 18, 2019, 12:06pm UTC](https://forum.networklessons.com/t/mpls-vpn-vrf-import-map/2405/3 "2019-01-18T12:06:03Z")

</div>

Hello Ignacio,

> In export-map, when you used it, it make other route-target in configuration statement useless.

That sounds correct, I noticed the same behavior in my [MPLS VPN export map example](https://networklessons.com/mpls/mpls-vpn-vrf-export-map).

> In import-maps both the import map and the route target are needed to work properly.

That sounds right too. Even with the import-map, you still see the VPN routes. The import map influences the VPN routes you import _into_ the VRF.

> Is there any other way to make this simpler? because I think there is no scalability in adding RT labels more and more.

Hmm I don’t think there is but you probably could do most of the work with the export-maps and regular `route-target import` commands. For simple sites where you don’t differentiate between the prefixes, you can use a single RT to export everything. Another site can import everything with a single RT.

For sites with multiple prefixes and you want to define who gets to import these prefixes, you must use an export-map to set different RTs per prefix. You can import them with the regular `route-target import` command.

Rene

---

_[View the full topic](https://forum.networklessons.com/t/mpls-vpn-vrf-import-map/2405)._