Comware Based
1820390 Members
3550 Online
109623 Solutions
New Discussion юеВ

GRE Tunnel - Line Protocol: Down

 
SOLVED
Go to solution
Colin_Painter
Occasional Contributor

GRE Tunnel - Line Protocol: Down

Hello,

I have a GRE tunnel that is running between a Comware 5510HI and MSR954. Both sides can ping the respective tunnel configured destinations however on the 5510 side, the line protocol is down.

I also have other GRE tunnels going from the same HP5510 to different MSR's which are working fine, config is replicated, so this is odd.

Here are the configs, IP's have been replaced..

HP5510:

interface Tunnel15 mode gre
description MPLS-TUNNEL
mtu 1360
bandwidth 300000
ip binding vpn-instance network-01
ip address 192.168.0.1 255.255.255.252
tcp mss 1320
source Vlan-interface250
destination 10.1.1.1
keepalive 10 3
#
interface Vlan-interface250
description "PUBLIC"
ip address 10.10.1.1 255.255.255.0
#

 

HP MSR:

interface Tunnel1 mode gre
description MPLS Link
mtu 1360
bandwidth 300000
ip address 192.168.0.2 255.255.255.252
tcp mss 1320
source GigabitEthernet0/0
destination 10.10.1.1
keepalive 10 3
#
interface GigabitEthernet0/0
description "PUBLIC"
ip address 10.1.1.1 255.255.255.0
#

 

Any t-shooting advice, as i cannot see where an issue may be... 

2 REPLIES 2
jmpk
HPE Pro

Re: GRE Tunnel - Line Protocol: Down

Hello ,

From the config i could see that you have binded a VPN instance on 5510 and you have not  used VPN instance on MSR , Can you please check on this ?

Thanks,

JMPK

I work fo HPE


I work for HPEAccept or Kudo
Colin_Painter
Occasional Contributor
Solution

Re: GRE Tunnel - Line Protocol: Down

Thanks for your reply. This isn't the problem though, on the HP MSR it has a WAN link which the other side of the interface is tagged for the VPN-instance.

For reference, I got this working by changing the destination to a new end point, then changing back again to original end point. For whatever reason it had got stuck, deciding it could not reach the destination, so removing the destination config and re-adding the same destination had no effect and 'shut', 'no shut' had no effect. Maybe a bug? Only by using a different destination end point, getting the tunnel up/up, then re-configuring to previous end point worked.