We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is Why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 622 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

444 New Members signed up the last 30 days!

satisfaction-guaranteed

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags: , ,


Forum Replies

  1. Thanks Rene - so am I right in thinking there is no implicit deny on a route map used as an export map in this process? Anything not matched on the route-map will just use the default settings configured.

    Normally when applying a route-map to a neighbour in IPv4 (e.g. neighbor X route-map Y) if something isn’t positively matched in the route-map, it will get dropped?

  2. Hi Chris,

    It still has the implicit deny but when you use a route-map as an export-map, it only tells the router which route-targets to add. When you use a route-map with a neighbor for a routing protocol, it works as a filter for routes.

    For example, this is the default route-target on PE1:

    ip vrf CUSTOMER
     rd 1:1
     route-target export 1:1:
    

    And we use this export-map:

    PE1(config)#ip prefix-list CE1_L0 permit 1.1.1.1/32
    PE1(config)#route-map EXPORT_MAP permit 10
    PE1(config-route-map)#match ip address prefix-list CE1_L0
    

    Then we end up with:

    PE1#show ip bgp vpnv
    ... Continue reading in our forum

Ask a question or join the discussion by visiting our Community Forum