07-22-2016 02:19 AM
Hello guys! I am trying to create a GRE Tunnel like in the next diagram:
What I am trying to to is (IP adresses are for example only):
1. R-VRF
Gi1/12.200 must be in the default routing table as such:
interface Gi1/12.200
encapsulation dot1q200
ip address 192.168.0.1 255.255.255.248
***ip vrf forwarding VRF_WAN
interface Tunnel111
ip vrf forwarding VRF_LAN
ip vrf sitemap DEFAULT_BGP
ip address 192.168.1.1 255.255.255.248
no ip split-horizon eigrp 100
keepalive 10 5
tunnel source GigabitEthernet1/12.200
tunnel destination 192.168.0.2
***tunnel vrf VRF_WAN
With the *** commands the tunnel works, but I want to make the tunnel work without vrf aware implemented, so I want to exclude the *** commands from above.
If I exclude the commands, the physical ping still works.
2.For R-CPE (not vrf aware):
interface BVI10
ip address 192.168.0.2 255.255.255.248
ip flow ingress
ip flow egress
interface Tunnel111
ip address 192.168.1.2 255.255.255.248
keepalive 10 5
tunnel source BVI10
tunnel destination 192.168.0.1
bridge 10 protocol ieee
bridge route ip
interface ATM1/0.1 point-to-point (DON'T ASK ME WHY I USE ATM _ because it's in the manual :))) )
bridge-group 10
pvc WAN_DATA 0/1
encapsulation aal5snap
protocol ip 192.168.0.1 broadcast
What do I do wrong that the tunnel does not work if I take out the commands marked in ***, as in I make the tunnel not vrf aware at the R-VRF side?
Thanks in advance!
07-23-2016 05:48 PM
Marius,
At the first sight, there is no obvious error in your configuration.
What does it exactly mean that the tunnel is "not working" when you remove the commands marked with ***? How exactly are you doing the connectivity test? Can you please post any relevant command and its output that shows the tunnel as being inoperative?
Best regards,
Peter
07-29-2016 11:32 AM
Hi,
as far as I know, you can use GRE keepalives only when the tunnel- and the source-interface are in the same VRF/context. In your working config the tunnel-VRF is "VRF_LAN" whereas the transport-VRF is "VRF_WAN", is this correct?
You could try to remove the tunnel keepalives or configure a hostroute to the tunnel destination in the tunnel-VRF with the tunnel source interface (global context) as exit-interface:
ip route vrf VRF_LAN 192.168.0.2 255.255.255.255 Gi1/12.200
HTH
Rolf
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