GRE Tunnel Protocol Down - Any help would be Awesome

[jasonbutryn]

See the attached:

Cant figure out why the tunnel had a 'down' protocol.

If you need more info from the routers...Let me know.  Thanx Team.

[jasonbutryn]

The Topology of the exercise:

[Diana Karolina Rojas]

Hello,

A valid tunnel source consists of any interface that is itself in the up/up state and has an IP address configured on it, are you ussing a Loopback interface as a Tunnel source for both sides?

Regards,

[jasonbutryn]

I am not using a loopback interface. 

[Diana Karolina Rojas]

Can you provide me the configuration of both tunnel sides?

Thank you,

[jasonbutryn]

Is the sh int Tunnel output I attached not enough information on the tunnels.  What other information would I find helpful? Thank you

[jasonbutryn]

Here you go.  Sorry for the late response. 

[Julio E. Moisa]

Hi

The first rule when you are implementing Gre tunnel is that the source and destination must be reachable. Verify if you are receiving the destination IP addresses on your routing table through OSPF.

or you can make ping between these IP addresses in order to verify.

For example:

FOX13 should be able to reach the ip address 10.4.14.2  and  FOX14 should be able to reach the ip addreses 10.13.2.2.

Are you including these tunnels into the VRF?

Hope it is useful

:-)

[Julio E. Moisa]

Hi,

Please see my configuration:

Note: Im not including the tunnel into the VRF but Im using the command tunnel vrf PIPE, to specify that Im going to use the source/destination into the VRF, but the tunnel will not be part of the VRF.

ROUTER 1

ip vrf PIPE
rd 1:1

interface Loopback0
ip vrf forwarding PIPE
ip address 1.1.1.1 255.255.255.255
ip ospf 1 area 0
!
interface Tunnel0
ip address 19.19.19.1 255.255.255.0
tunnel source Loopback0
tunnel destination 9.9.9.9
tunnel vrf PIPE
!
interface FA0/0
ip vrf forwarding PIPE
ip address 10.13.2.1 255.255.255.248
!
interface FA0/1
ip address 10.1.2.1 255.255.255.0
ip summary-address eigrp 1 0.0.0.0 0.0.0.0
!

!
!
router eigrp 1
network 10.1.2.1 0.0.0.0
!
router ospf 1 vrf PIPE
network 1.1.1.1 0.0.0.0 area 0
network 10.13.2.1 0.0.0.0 area 0
!

ip route 0.0.0.0 0.0.0.0 19.19.19.9

R1#SH INT TU0
Tunnel0 is up, line protocol is up
Hardware is Tunnel
Internet address is 19.19.19.1/24
MTU 17916 bytes, BW 100 Kbit/sec, DLY 50000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel linestate evaluation up
Tunnel source 1.1.1.1 (Loopback0), destination 9.9.9.9
Tunnel Subblocks:
src-track:
Tunnel0 source tracking subblock associated with Loopback0
Set of tunnels with source Loopback0, 1 member (includes iterators), on interface <OK>
Tunnel protocol/transport GRE/IP
Key disabled, sequencing disabled
Checksumming of packets disabled

R1#show ip route vrf PIPE 9.9.9.9

Routing Table: PIPE
Routing entry for 9.9.9.9/32
Known via "ospf 1", distance 110, metric 21, type intra area
Last update from 10.13.2.2 on FastEthernet0/0, 00:10:49 ago
Routing Descriptor Blocks:
* 10.13.2.2, from 10.0.29.9, 00:10:49 ago, via FastEthernet0/0
Route metric is 21, traffic share count is 1

ROUTER 2

interface Loopback0
ip vrf forwarding PIPE
ip address 9.9.9.9 255.255.255.255
!
interface Tunnel0
ip address 19.19.19.9 255.255.255.0
tunnel source Loopback0
tunnel destination 1.1.1.1
tunnel vrf PIPE
!
interface FA0/0
ip address 10.0.109.9 255.255.255.0
ip summary-address eigrp 1 0.0.0.0 0.0.0.0
!
interface FA0/1
ip vrf forwarding PIPE
ip address 10.0.29.9 255.255.255.0
!
!
router eigrp 1
network 10.0.109.0 0.0.0.255
!
router ospf 1 vrf PIPE
network 9.9.9.9 0.0.0.0 area 0
network 10.0.29.9 0.0.0.0 area 0

ip route 0.0.0.0 0.0.0.0 19.19.19.1

R2#SH INT TU0
Tunnel0 is up, line protocol is up
Hardware is Tunnel
Internet address is 19.19.19.9/24
MTU 17916 bytes, BW 100 Kbit/sec, DLY 50000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel linestate evaluation up
Tunnel source 9.9.9.9 (Loopback0), destination 1.1.1.1
Tunnel Subblocks:
src-track:
Tunnel0 source tracking subblock associated with Loopback0
Set of tunnels with source Loopback0, 1 member (includes iterators), on interface <OK>
Tunnel protocol/transport GRE/IP
Key disabled, sequencing disabled
Checksumming of packets disabled

R2#sh ip route vrf PIPE 1.1.1.1

Routing Table: PIPE
Routing entry for 1.1.1.1/32
Known via "ospf 1", distance 110, metric 21, type intra area
Last update from 10.0.29.2 on FastEthernet0/1, 00:18:41 ago
Routing Descriptor Blocks:
* 10.0.29.2, from 10.13.2.1, 00:18:41 ago, via FastEthernet0/1
Route metric is 21, traffic share count is 1
R2#

CLIENT 1

r11#ping 10.10.10.10 source 11.11.11.11 repeat 100
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 10.10.10.10, timeout is 2 seconds:
Packet sent with a source address of 11.11.11.11
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (100/100), round-trip min/avg/max = 1/1/2 ms
r11#

r11#traceroute 10.10.10.10 source 11.11.11.11 numeric
Type escape sequence to abort.
Tracing the route to 10.10.10.10
VRF info: (vrf in name/id, vrf out name/id)
1 10.1.2.1 0 msec 1 msec 0 msec
2 19.19.19.9 1 msec 1 msec 0 msec    <---- tunnel
3 10.0.109.10 1 msec * 2 msec
r11#

CLIENT 2

R10#ping 11.11.11.11 source 10.10.10.10 repeat 100
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 11.11.11.11, timeout is 2 seconds:
Packet sent with a source address of 10.10.10.10
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (100/100), round-trip min/avg/max = 1/1/1 ms
R10#

R10#traceroute 11.11.11.11 sou
R10#traceroute 11.11.11.11 source 10.10.10.10 numeric
Type escape sequence to abort.
Tracing the route to 11.11.11.11
VRF info: (vrf in name/id, vrf out name/id)
1 10.0.109.9 0 msec 0 msec 1 msec
2 19.19.19.1 0 msec 1 msec 1 msec     <--- tunnel
3 10.1.2.11 1 msec * 1 msec
R10#

In few words, I am using OSPF with VRF but EIGRP is using the global routing table, To enable the communication between the clients is possible because Im using tunnel vrf comand. This command is different than ip vrf forwarding <vrf>, it is used to associate an interface to the vrf. But if you want you could use your entire topology over the vrf PIPE. 

Please rate the comment if was useful 

:-)

[jasonbutryn]

Hi Julio... I cannot Ping either IP address from wither router. I will look at your below configs very closley.  Thank you

[Julio E. Moisa]

You are welcome my friend,

Any doubts, we will be here to assist you. Or you can share your config to verify it. I have used loopbacks but you could use other interface into the VRF. 

:-)

[jasonbutryn]

Do I need to config the loopback0 interface for the tunnel? I have assigned a source and destination IP. 

[Julio E. Moisa]

Hi

Actually you could use any interface but into the VRF and associated to the OSPF

:-) 

Let me lab it without loopback as source or destination and share it with you.

[Julio E. Moisa]

Hi

Here we go, Im not using the loopbacks as source or destination. Please see the diagram.

ROUTER 1

ip vrf PIPE
rd 1:1

interface Tunnel100
ip address 13.13.13.1 255.255.255.0
tunnel source 10.12.0.1
tunnel destination 10.23.0.3
tunnel vrf PIPE
!
interface Fa0/0
ip vrf forwarding PIPE
ip address 10.12.0.1 255.255.255.0
!
interface Fa0/1
ip address 10.111.0.1 255.255.255.0
ip summary-address eigrp 1 0.0.0.0 0.0.0.0
!

router eigrp 1
network 10.111.0.1 0.0.0.0
!
router ospf 1 vrf PIPE
network 10.12.0.1 0.0.0.0 area 0
!
ip forward-protocol nd
!
!
no ip http server
no ip http secure-server
ip route 0.0.0.0 0.0.0.0 13.13.13.3 name DEFAULT-ROUTE

R1#sh ip int brief | include Tunnel
Tunnel100 13.13.13.1 YES manual  up    up

ROUTER 2

ip vrf PIPE
rd 1:1

interface Fa0/0
ip vrf forwarding PIPE
ip address 10.12.0.2 255.255.255.0
!
interface Fa0/1
ip vrf forwarding PIPE
ip address 10.23.0.2 255.255.255.0
!
!
router ospf 1 vrf PIPE
network 0.0.0.0 255.255.255.255 area 0

ROUTER 3

ip vrf PIPE
rd 1:1

interface Tunnel100
ip address 13.13.13.3 255.255.255.0
tunnel source 10.23.0.3
tunnel destination 10.12.0.1
tunnel vrf PIPE
!
interface Fa0/0
ip address 10.103.0.3 255.255.255.0
ip summary-address eigrp 1 0.0.0.0 0.0.0.0
!
interface Fa0/1
ip vrf forwarding PIPE
ip address 10.23.0.3 255.255.255.0
!
!
router eigrp 1
network 10.103.0.3 0.0.0.0
!
router ospf 1 vrf PIPE
network 10.23.0.3 0.0.0.0 area 0
!

ip route 0.0.0.0 0.0.0.0 13.13.13.1 name DEFAULT-ROUTE

R3#sh ip int brief | include Tunnel
Tunnel100 13.13.13.3 YES manual  up   up

ROUTER 10

interface Loopback0
ip address 10.10.10.10 255.255.255.255
!
interface Ethernet0/0
ip address 10.103.0.10 255.255.255.0
!
!
router eigrp 1
network 0.0.0.0

R10#traceroute 11.11.11.11 source 10.10.10.10 numeric
Type escape sequence to abort.
Tracing the route to 11.11.11.11
VRF info: (vrf in name/id, vrf out name/id)
1 10.103.0.3 1 msec 0 msec 1 msec
2 13.13.13.1 2 msec 1 msec 1 msec
3 10.111.0.11 1 msec * 4 msec
R10#

ROUTER 11

interface Loopback0
ip address 11.11.11.11 255.255.255.255
!
interface Ethernet0/0
ip address 10.111.0.11 255.255.255.0

!
router eigrp 1
network 0.0.0.0

r11#traceroute 10.10.10.10 source 11.11.11.11 numeric
Type escape sequence to abort.
Tracing the route to 10.10.10.10
VRF info: (vrf in name/id, vrf out name/id)
1 10.111.0.1 1 msec 0 msec 1 msec
2 13.13.13.3 1 msec 2 msec 1 msec
3 10.103.0.10 1 msec * 2 msec
r11#

Hope it is useful

:-)

[jasonbutryn]

Julio,

Im going to post the run conf of the routers. They look so similar. I am missing something.  (I wish I could share my screen with you... LOL)

This is just a lab but I want to know the how, not just the answer