# MPLS VPN VRF Export Map

**URL:** <https://forum.networklessons.com/t/mpls-vpn-vrf-export-map/2384>\
**Category:** Lessons Discussion\
**Created:** [November 9, 2017, 11:44am UTC](https://forum.networklessons.com/t/mpls-vpn-vrf-export-map/2384 "2017-11-09T11:44:55Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![lagapidis](https://cdn-forum.networklessons.com/user_avatar/forum.networklessons.com/lagapidis/32/4949_2.png) [@lagapidis](https://forum.networklessons.com/u/lagapidis)\
**Post date:** [February 4, 2019, 11:48am UTC](https://forum.networklessons.com/t/mpls-vpn-vrf-export-map/2384/5 "2019-02-04T11:48:00Z")

</div>

Hello Zaman

The additive keyword will allow you to add an export map without overwriting the previously configured ones. For example, if you configure the following:

```
PE1(config)#route-map EXPORT_MAP permit 10         
PE1(config-route-map)#set extcommunity rt 1:1 

```

and then at a later time you configure this:

```
PE1(config)#route-map EXPORT_MAP permit 10         
PE1(config-route-map)#set extcommunity rt 3:3 

```

The result is that the 1:1 entry will be overwritten by the 3:3 entry. However, if you use the `additive` keyword like this instead:

```
PE1(config)#route-map EXPORT_MAP permit 10         
PE1(config-route-map)#set extcommunity rt 3:3 additive

```

Then 3:3 will not overwrite 1:1 but will be added to it.

I hope this has been helpful!

Laz

---

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