02-11-2017 10:13 AM - edited 03-08-2019 09:17 AM
Hello,
I am having issues getting my VRF routes to talk to my global route. I can ping from Global to VRF. I have been following this guide: Route Leaking in MPLS/VPN Networks. It works up until the portion where I have to enter my VRF route to global. I keep getting an error: % For VPN or topology
For the route, I tried to input:
and
ip |
A little lost with what I am doing wrong or what else I need to do. Any insight on this issue would be greatly appreciated. Thanks.
Solved! Go to Solution.
02-12-2017 06:10 AM
Actually after inspecting your original configuration further, is the purpose of the route leaking to allow the Computers VRF to use next-hop 192.168.5.1 for networks that are not local to this router such as for internet access? If so, we can remove the import ipv4 unicast map configuration that we have applied above and simply apply the following static routes
ip route 192.168.52.0 255.255.255.248 GigabitEthernet0/1.25
ip route vrf Computers 0.0.0.0 0.0.0.0 GigabitEthernet0/0 192.168.5.1 global
02-11-2017 12:42 PM
Hi,
I have implemented something similar before by using BGP to share routes between VRFs using route-targets and then using an import ipv4 unicast map to import prefixes from the Global VRF.
Example config
router bgp 65000
no bgp default ipv4-unicast
bgp log-neighbor-changes
!
address-family ipv4
no auto-summary
no synchronization
network 192.168.5.0 mask 255.255.255.252
exit-address-family
!
address-family ipv4 vrf Wi-Fi
redistribute connected
no synchronization
exit-address-family
!
address-family ipv4 vrf Servers
redistribute connected
no synchronization
exit-address-family
!
address-family ipv4 vrf Computers
redistribute connected
no synchronization
exit-address-family
ip prefix-list Gig0/0-NET seq 5 permit 192.168.5.0/30
route-map IMPORT-GLOBAL permit 10
match ip address prefix-list Gig0/0-NET
ip vrf Computers
import ipv4 unicast map IMPORT-GLOBAL
Hope this helps.
02-11-2017 07:44 PM
Will,
Thanks for the reply. I tried this example as well. I can see the route being learned via BGP now, but I still cannot reach those IP address.
LAN_Sec_Router(config)#$ Computers ip 192.168.5.1 source 192.168.52.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.5.1, timeout is 2 seconds: Packet sent with a source address of 192.168.52.1 ... Success rate is 0 percent (0/3) |
LAN_Sec_Router#show Routing Table: Computers Routing Table: Computers Gateway of last resort is not set 192.168.5.0/30 is subnetted, 1 subnets |
router
|
02-12-2017 12:21 AM
Hi,
Do you still have the following static route in place in the global routing table?
ip route 192.168.52.0 255.255.255.248 GigabitEthernet0/1.25
Also can you try and ping the routers local Gig0/0 IP address 192.168.5.2 from VRF Computers? If this is successful then there may be a routing issue with the next hop device.
02-12-2017 06:10 AM
Actually after inspecting your original configuration further, is the purpose of the route leaking to allow the Computers VRF to use next-hop 192.168.5.1 for networks that are not local to this router such as for internet access? If so, we can remove the import ipv4 unicast map configuration that we have applied above and simply apply the following static routes
ip route 192.168.52.0 255.255.255.248 GigabitEthernet0/1.25
ip route vrf Computers 0.0.0.0 0.0.0.0 GigabitEthernet0/0 192.168.5.1 global
02-12-2017 07:17 AM
Will,
Correct, the purpose of the route leaking is to allow the Computers VRF to communicate with the 192.168.5.0/30 network to access the Internet.
I removed the previous ipv4 unicast map configurations and put in the static route:
*Feb 12 15:07:27.399: ICMP:
02-12-2017 07:42 AM
Can you post the output of 'show ip route'
Also does the router with IP 192.168.5.1 have a route back to 192.168.52.0/29 with a next-hop IP address of 192.168.5.2?
02-12-2017 07:54 AM
Will,
Certainly, give me a moment and I'll swap over. Unfortunately, every time I try to make changes and post them on here I have to disconnect from the Internet.
02-12-2017 08:05 AM
Will,
Here is the "show
LAN_Sec_Router#show Gateway of last resort is 192.168.5.1 to network 0.0.0.0 S* 0.0.0.0/0 [1/0] via 192.168.5.1 Routing Table: Computers Gateway of last resort is 192.168.5.1 to network 0.0.0.0 S* 0.0.0.0/0 [1/0] via 192.168.5.1, GigabitEthernet0/0 |
Here's the "show
WAN_Router#show ip route Gateway of last resort is *.*.*.* to network 0.0.0.0 S* 0.0.0.0/0 [1/0] via *.*.*.* |
02-12-2017 08:33 AM
Thanks.
The configuration all looks ok from what I can see and the successful pings to 192.168.52.1 and the router behind the LAN_Sec_Router 192.168.52.2 from the WAN Router is positive. However, it’s odd that you are unable to ping from 192.168.52.1.
Is it only pings to 192.168.5.2 from the Computers VRF that fails? How about pings to 192.168.5.1 or other interfaces local to the WAN Router? Also do have the same issue when pinging from 192.168.52.2?
When you test again can you also debug ICMP on the WAN router as this may indicate why its sending a host unreachable message.
02-12-2017 09:41 AM
Will,
Here's the debug packet I received from the WAN_Router. It only has one port to ping from. The other side is connected to a switch that cannot ping the router, but it passes the modem's traffic to the router.
WAN_Router#ping 192.168.52.1 source 192.168.5.1 WAN_Router#ping 192.168.52.2 source 192.168.5.1 |
LAN_Sec_Router#ping *Feb 12 17:36:06.099: ICMP: echo reply sent, src 192.168.5.2, dst 192.168.254.26, topology BASE, dscp 0 topoid 0. |
LAN_Switch#ping Type escape sequence to abort. Type escape sequence to abort. |
So, it seems to work from the switch and PC to reach 192.168.5.1 and 192.168.5.2, but I cannot reach it for some odd reason from the router??? Little confused by this. There is another VRF I want to achieve this same functionality with, but I never tried to set it up as I have been trying to troubleshoot this one for a while now.
02-12-2017 09:50 AM
Ok according to the below debug, when you ping 192.168.5.2 from the Computers VRF the echo reply is being sent back to 192.168.254.26. I can see that 192.168.254.26 is the loopback26 interface in the Computers VRF
LAN_Sec_Router#ping vrf Computers ip 192.168.5.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.5.2, timeout is 2 seconds:
*Feb 12 17:36:06.099: ICMP: echo reply sent, src 192.168.5.2, dst 192.168.254.26, topology BASE
Can you try pinging again with a source of 192.168.52.1?
ping vrf Computers ip 192.168.5.2 source 192.168.52.1
ping vrf Computers ip 192.168.5.1 source 192.168.52.1
02-12-2017 10:01 AM
Will,
When doing a source ping, I can ping 192.168.5.1, but I cannot ping 192.168.5.2 still.
LAN_Sec_Router#ping vrf Computers 192.168.5.2 source 192.168.52.1 *Feb 12 17:59:20.950: ICMP: echo reply sent, src 192.168.5.2, dst 192.168.52.1, topology BASE, dscp 0 topoid 0 |
02-12-2017 10:13 AM
Ok that is odd and I cannot see a reason why that would happen.
I have just tested your setup on a couple of routers and it works for me without any issues. What model of router is this and what IOS version is it running?
From a functionality perspective, will this behaviour cause you an issue as traffic transiting the router between the Computers VRF and Global Routing table now seems to be working as expected?
02-12-2017 10:28 AM
Will,
Since my PC was able to reach 192.168.5.1 just fine, I don't think there will be any issues functionality with this behavior.
I am also running 15.1(4)M9 on a 3945 Cisco router with AdventerpriseK9.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide