Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Route Leaking in MPLS/VPN Networks

Hi All,

I have been looking at the example in http://www.cisco.com/en/US/tech/tk436/tk832/technologies_configuration_example09186a0080231a3e.shtml

My implementation is almost identical, I have a Netflow Collector sitting in my Management vrf.

The global route is working fine and my flows are getting to the collector, but my issue is the return path.

My source interface is a loopback address and whenever I try to add a route to it I get:

ip route vrf vpn2 10.1.1.1 255.255.255.255 Loopback0

% For VPN routes, must specify a next hop IP address if not a point-to-point interface.

My question is:

What should the next hop address be in this case.

I have also tried:

ip route vrf vpn2 10.1.1.1 255.255.255.255 Loopback0 10.1.1.1

with no success.

Sorry if I havnt explained the problem too well, please let me know if you need any more information.

Thanks,

Aaron

4 REPLIES

Re: Route Leaking in MPLS/VPN Networks

Hello Aaron,

Your config should look similar to this:

ip route vrf vpn2 10.1.1.1 255.255.255.255 10.1.1.1 global

assuming your Loopback is in the global IP routing table.

Hope this helps! Please rate all posts.

Regards, Martin

New Member

Re: Route Leaking in MPLS/VPN Networks

Hi Martin,

I gave that a shot too,

I get the following:

ip route vrf vpn2 10.1.1.1 255.255.255.255 10.1.1.1 global

%Invalid next hop address (it's this router)

myrouter(config)#

Thanks,

Aaron

Re: Route Leaking in MPLS/VPN Networks

Hello Aaron,

the route example works for all routers except the one, where the VRF vpn2 is configured. What you can do for management purposes is either to connect through a neighbor router using packet leaking or configure another Loopback into VRF vpn2.

The last option (and my recommendation) is to establish another separate IP connection from your NMS to the MPLS core. Once VRFs are failing (for whatever reason, f.e. erroneously deleted) you might just not get connectivity to your backbone anymore to repair what went wrong.

So I would create an "interconnection router" with an interface in the VRF vpn2 and one interface in global IP routing table. This way you will still be able to access PEs, even if VRFs or MBGP is gone.

Hope this helps! Please rate all posts.

Regards, Martin

New Member

Re: Route Leaking in MPLS/VPN Networks

Hi There Aron

I can only imagine your Collector connected to the PE either directly or via a CE (!). In either case, I do not see how traffic can reach the Collector if the static route is pointed to Loopback0? with this logic the static route should be pointed to either a physical interface, subinterface or VSI

You also need to make sure reachability is advertised beyond the CE and/or PE where applicable

Regards

Ahmed

1195
Views
2
Helpful
4
Replies