cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
306
Views
0
Helpful
2
Replies

Cisco 7206vxr GRE tunnel intermittent down issue

HCL Support
Level 1
Level 1

Hi Team,

We have Cisco 7206vxr Router installed at the Customer site and facing issue as described below and our Observation during the Network gets unreachable.

1. Remote VSATs are up and next IP (Fa0/1) also reachable from DC-1 Router.snap shot attached
2. Local (DC router) Tunnels is up and pinging but branches tunnels is not pinging from DC router, ALL GRE tunnel was found down during this period
3. No bandwidth Utilization on WAN Interface (Gi0/2)
4. All branches LAN IP is unreachable and trace route dropped at DC-1 LAN IP address
5. After WAN interface Gig0/2 Shutdown & No shut, network comes to normal .

Debug tunnel output:-

Feb  2 23:18:40.689: Tunnel234: GRE/IP encapsulated 95.255.0.1->95.0.3.166 (link
type=7, len=48)
Feb  2 23:18:40.689: Tunnel234 count tx, adding 24 encap bytes

Also All the respective logs attached here and need further suggestion on this case if some bug impact or some Hardware impact.

Current IOS image: c7200p-advsecurityk9-mz.124-24.T8.bin

Regards,

Ashutosh

        

2 Replies 2

Hello.

your "sh tech" is showing that G0/2 is in admin down state, so all the other information is not interesting.

Could you please provide "sh tech" right after the issue occures (before you troubleshoot it), then try to shut/no shut interface (if it helps) and provide the log (you might need to increase log size, as 50K is not enough for 1K tunnels).

Could you please provide tunnel configuration from any site?

Is it possible to capture traffic on G0/2 during the issue (SPAN)? If capture is not possible, could you try:

ip access-l ext 199

permit ip host 95.255.0.1 host 95.0.16.170

permit ip host 95.0.16.170 host 95.255.0.1

debug ip pack 199

try pinging 95.0.16.170, pingning 32.254.16.170 and capture debug output for 60 seconds.

(please add "show ip route" as weel)

Try to clear counters on int g0/2 and check what's happening on the interface (CRC, runts, whatever).

Do you have any CoPP or service-policy applied to filter/rate limit any traffic on G0/2 ?

Hello

Looks like these basic gre tunnels?

Was 10.113.117.202 reachable and did you had NLRI between the source and destination tunnel addresses prior to you restarting gig0/2 manually?

I can see an acl relating to icmp but it seems it not alowing return traffic, Is this acl applied anywhere? I cannot see that it is or had it been?

Looking at you show tech readout, the interface counts have never been cleared so the history stats could be showing old values and the gig0.2 interface is in admin shutdown -Also a alot of static routing going on

At first glance of this, I suspect that a possible l issue on this gig0/2 link caused a lost of reacability to your branches thus dropping the tunnels which are only shown going down due you having keepalives applied.

The question is, if it was a issue with the line or the port and then why did you experience that issue,

Have you checked with your ISP for possible disuption to this link and it realting ports ( if applicable)

Have you checked the physical ports/cabling on this router?

res

Paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco