{"id":24580,"date":"2026-11-17T15:22:16","date_gmt":"2026-11-17T07:22:16","guid":{"rendered":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html"},"modified":"2026-11-17T15:22:16","modified_gmt":"2026-11-17T07:22:16","slug":"how-to-check-gre-tunnel-status-in-cisco-router","status":"publish","type":"post","link":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html","title":{"rendered":"How to Check GRE Tunnel Status in Cisco Router"},"content":{"rendered":"<p>Generic Routing Encapsulation (GRE) tunnels provide virtual point-to-point and multipoint connectivity across IP networks, enabling Cisco routers to transport routing protocols, multicast streams, and IPv6 payloads over an existing IPv4 or IPv6 underlay. Because a GRE tunnel is a logical construct rather than a physical wire, verifying whether it is truly operational requires checking more than just the local interface state. You must inspect line protocol conditions, packet counters, keepalive responses, and\u2014when encrypted\u2014the underlying IPsec security associations.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_17 counter-hierarchy counter-decimal ez-toc-light-blue\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" style=\"display: none;\"><i class=\"ez-toc-glyphicon ez-toc-icon-toggle\"><\/i><\/a><\/span><\/div>\n<nav><ul class=\"ez-toc-list ez-toc-list-level-1\"><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#Core_Cisco_IOS_CLI_Commands_to_Check_GRE_Tunnel_Status_and_Statistics\" title=\"Core Cisco IOS CLI Commands to Check GRE Tunnel Status and Statistics\">Core Cisco IOS CLI Commands to Check GRE Tunnel Status and Statistics<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#Understanding_GRE_Tunnel_States_and_How_Keepalives_Work\" title=\"Understanding GRE Tunnel States and How Keepalives Work\">Understanding GRE Tunnel States and How Keepalives Work<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#Why_does_a_Cisco_GRE_tunnel_stay_upup_when_the_remote_router_is_down\" title=\"Why does a Cisco GRE tunnel stay up\/up when the remote router is down?\">Why does a Cisco GRE tunnel stay up\/up when the remote router is down?<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#What_do_the_different_interface_and_line_protocol_status_combinations_mean\" title=\"What do the different interface and line protocol status combinations mean?\">What do the different interface and line protocol status combinations mean?<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#How_do_GRE_tunnel_keepalives_detect_remote_peer_status\" title=\"How do GRE tunnel keepalives detect remote peer status?\">How do GRE tunnel keepalives detect remote peer status?<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#Verifying_GRE_over_IPsec_Tunnel_and_Crypto_Session_Status\" title=\"Verifying GRE over IPsec Tunnel and Crypto Session Status\">Verifying GRE over IPsec Tunnel and Crypto Session Status<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#Step-by-Step_Guide_to_Troubleshooting_Down_or_Flapping_GRE_Tunnels\" title=\"Step-by-Step Guide to Troubleshooting Down or Flapping GRE Tunnels\">Step-by-Step Guide to Troubleshooting Down or Flapping GRE Tunnels<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#Step_1_Query_the_Internal_Tunnel_Line_State_Evaluation_Reason\" title=\"Step 1: Query the Internal Tunnel Line State Evaluation Reason\">Step 1: Query the Internal Tunnel Line State Evaluation Reason<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#Step_2_Validate_Underlay_Routing_and_IP_Protocol_47_Reachability\" title=\"Step 2: Validate Underlay Routing and IP Protocol 47 Reachability\">Step 2: Validate Underlay Routing and IP Protocol 47 Reachability<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#Step_3_Resolve_Recursive_Routing_Flaps\" title=\"Step 3: Resolve Recursive Routing Flaps\">Step 3: Resolve Recursive Routing Flaps<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#Step_4_Debug_Keepalive_Drops_and_MTU_Blackholes\" title=\"Step 4: Debug Keepalive Drops and MTU Blackholes\">Step 4: Debug Keepalive Drops and MTU Blackholes<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#Automated_Tools_and_SNMP_Methods_for_Monitoring_Cisco_GRE_Tunnels\" title=\"Automated Tools and SNMP Methods for Monitoring Cisco GRE Tunnels\">Automated Tools and SNMP Methods for Monitoring Cisco GRE Tunnels<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#Official_Cisco_IOS_Documentation_and_Command_References_for_GRE\" title=\"Official Cisco IOS Documentation and Command References for GRE\">Official Cisco IOS Documentation and Command References for GRE<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\/#Conclusion\" title=\"Conclusion\">Conclusion<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Core_Cisco_IOS_CLI_Commands_to_Check_GRE_Tunnel_Status_and_Statistics\"><\/span>Core Cisco IOS CLI Commands to Check GRE Tunnel Status and Statistics<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>To verify whether a GRE tunnel interface is active and forwarding traffic on a Cisco IOS or IOS XE router, use the following privileged EXEC commands. Replace <code>&lt;number&gt;<\/code> with your configured tunnel interface ID.<\/p>\n<pre><code class=\"language-ios\">! 1. Quick summary of administrative and line protocol status for all tunnels\nRouter# show ip interface brief | include Tunnel\nTunnel0                10.255.0.1      YES NVRAM  up                    up      \nTunnel1                10.255.0.5      YES NVRAM  up                    down    \n<\/code><\/pre>\n<pre><code class=\"language-ios\">! 2. Detailed inspection of GRE parameters, keepalives, MTU, and traffic counters\nRouter# show interfaces tunnel &lt;number&gt;\nTunnel0 is up, line protocol is up \n  Hardware is Tunnel\n  Internet address is 10.255.0.1\/30\n  MTU 17916 bytes, BW 100 Kbit\/sec, DLY 50000 usec, \n     reliability 255\/255, txload 1\/255, rxload 1\/255\n  Encapsulation TUNNEL, loopback not set\n  Keepalive set (10 sec), retries 3\n  Tunnel linestate evaluation up\n  Tunnel source 203.0.113.1 (GigabitEthernet0\/0), destination 198.51.100.1\n   Tunnel Subblocks:\n      src-track:\n         Tunnel0 source tracking subblock associated with GigabitEthernet0\/0\n          Set of tunnels with source GigabitEthernet0\/0, 1 member (includes iterators), on interface &lt;OK&gt;\n  Tunnel protocol\/transport GRE\/IP\n    Key disabled, sequencing disabled\n    Checksumming of packets disabled\n  Tunnel TTL 255, Fast tunneling enabled\n  Tunnel transport MTU 1476 bytes\n  Tunnel transmit bandwidth 8000 (kbps)\n  Tunnel receive bandwidth 8000 (kbps)\n  Last input 00:00:02, output 00:00:02, output hang never\n  Last clearing of &quot;show interface&quot; counters never\n  Input queue: 0\/375\/0\/0 (size\/max\/drops\/flushes); Total output drops: 0\n  Queueing strategy: fifo\n  Output queue: 0\/0 (size\/max)\n  5 minute input rate 142000 bits\/sec, 38 packets\/sec\n  5 minute output rate 156000 bits\/sec, 41 packets\/sec\n     28450 packets input, 19842100 bytes, 0 no buffer\n     Received 0 broadcasts (0 IP multicasts)\n     0 runts, 0 giants, 0 throttles \n     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort\n     31204 packets output, 21490800 bytes, 0 underruns\n     0 output errors, 0 collisions, 0 interface resets\n<\/code><\/pre>\n<pre><code class=\"language-ios\">! 3. Verify the active configuration applied to the tunnel interface\nRouter# show running-config interface tunnel &lt;number&gt;\nBuilding configuration...\n\nCurrent configuration : 194 bytes\n!\ninterface Tunnel0\n ip address 10.255.0.1 255.255.255.252\n ip mtu 1400\n ip tcp adjust-mss 1360\n keepalive 10 3\n tunnel source GigabitEthernet0\/0\n tunnel destination 198.51.100.1\nend\n<\/code><\/pre>\n<p>Key fields to validate in the output above:<br \/>\n* <strong><code>Tunnel0 is up, line protocol is up<\/code><\/strong>: Confirms both the administrative state and local protocol checks (or active keepalives) have succeeded.<br \/>\n* <strong><code>Tunnel source ... destination ...<\/code><\/strong>: Displays the underlay IP addresses and physical source interface binding (<code>&lt;OK&gt;<\/code>).<br \/>\n* <strong><code>Keepalive set<\/code><\/strong>: Indicates whether active end-to-end health probing is enabled (<code>Keepalive not set<\/code> appears by default).<br \/>\n* <strong><code>Tunnel transport MTU<\/code><\/strong>: Shows the automatically calculated maximum payload size after accounting for the 24-byte GRE + outer IPv4 header overhead (1500 \u2212 24 = 1476 bytes).<br \/>\n* <strong><code>packets input<\/code> \/ <code>packets output<\/code><\/strong>: Confirms bidirectional encapsulation (<code>output<\/code>) and decapsulation (<code>input<\/code>) across the tunnel.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Understanding_GRE_Tunnel_States_and_How_Keepalives_Work\"><\/span>Understanding GRE Tunnel States and How Keepalives Work<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Seeing an operational status in the CLI output does not always guarantee end-to-end reachability. Because GRE behaves differently from physical links, interpreting its status combinations requires understanding how Cisco IOS evaluates virtual interfaces.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Why_does_a_Cisco_GRE_tunnel_stay_upup_when_the_remote_router_is_down\"><\/span>Why does a Cisco GRE tunnel stay up\/up when the remote router is down?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>By design, GRE (defined in RFC 2784, using IP Protocol 47) is a stateless encapsulation protocol with no built-in control plane or handshake. When keepalives are not configured, a Cisco router evaluates only local criteria before placing a point-to-point GRE tunnel into the <code>up\/up<\/code> state:<br \/>\n1. The tunnel interface is not administratively shut down.<br \/>\n2. The configured <code>tunnel source<\/code> interface is in the <code>up\/up<\/code> state and has a valid IP address assigned.<br \/>\n3. The router has a valid route in its Routing Information Base (RIB) to reach the <code>tunnel destination<\/code> IP address (including a default route <code>0.0.0.0\/0<\/code>), and that route does not point out the tunnel interface itself.<\/p>\n<p>If the remote peer powers off or an intermediate ISP drops GRE packets, the local router&#8217;s underlay route to the destination IP often remains valid (for example, via a default gateway), causing the tunnel to remain <code>up\/up<\/code> and blackhole traffic.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_do_the_different_interface_and_line_protocol_status_combinations_mean\"><\/span>What do the different interface and line protocol status combinations mean?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong><code>TunnelX is up, line protocol is up<\/code><\/strong>: All local source and routing checks pass, and if keepalives are enabled, keepalive responses are actively arriving from the remote endpoint.<\/li>\n<li><strong><code>TunnelX is up, line protocol is down<\/code><\/strong>: The tunnel interface is enabled, but a protocol dependency has failed. Common causes include: no route in the routing table to the <code>tunnel destination<\/code>, the physical <code>tunnel source<\/code> interface is down, consecutive GRE keepalive probes have timed out, or the tunnel source tracks an inactive HSRP\/redundancy virtual IP.<\/li>\n<li><strong><code>TunnelX is administratively down, line protocol is down<\/code><\/strong>: The <code>shutdown<\/code> command is currently applied under <code>interface TunnelX<\/code>.<\/li>\n<li><strong><code>TunnelX is down, line protocol is down<\/code><\/strong>: The logical interface has failed initialization due to a critical hardware or software subblock error.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"How_do_GRE_tunnel_keepalives_detect_remote_peer_status\"><\/span>How do GRE tunnel keepalives detect remote peer status?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Configuring <code>keepalive [period [retries]]<\/code> (defaulting to every 10 seconds with 3 retries) under the tunnel interface enables active end-to-end path verification without requiring software changes on the remote peer:<br \/>\n1. <strong>Packet Construction<\/strong>: The local router pre-builds an inner GRE keepalive response packet with its own tunnel source IP as the destination and the remote tunnel endpoint IP as the source.<br \/>\n2. <strong>Encapsulation &amp; Transmission<\/strong>: It wraps that inner packet inside a standard outer GRE header addressed to the remote <code>tunnel destination<\/code> IP and transmits it.<br \/>\n3. <strong>Stateless Echo at Remote Peer<\/strong>: When the remote router receives the packet on IP Protocol 47, it strips the outer GRE header, inspects the inner IP header, sees that the destination IP belongs to the originating router, and routes the inner GRE packet right back to the sender.<br \/>\n4. <strong>State Enforcement<\/strong>: If the originating router misses the configured number of consecutive keepalive returns (for example, 3 missed packets at 10-second intervals = 30 seconds), it brings the tunnel line protocol <code>down<\/code>, allowing dynamic routing protocols or floating static routes to fail over immediately.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Verifying_GRE_over_IPsec_Tunnel_and_Crypto_Session_Status\"><\/span>Verifying GRE over IPsec Tunnel and Crypto Session Status<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Because standard GRE does not encrypt payloads, production deployments frequently pair GRE with IPsec (<code>tunnel protection ipsec profile &lt;profile-name&gt;<\/code>). In a GRE over IPsec architecture, the GRE line protocol depends on the underlying IKE (Phase 1) and IPsec (Phase 2) Security Associations (SAs). Use the following CLI commands to verify both layers simultaneously.<\/p>\n<pre><code class=\"language-ios\">! 1. Verify unified crypto session state mapped to the Tunnel interface\nRouter# show crypto session detail\nCrypto session current status\n\nCode: C - IKE Configuration mode, D - Dead Peer Detection     \nK - Keepalives, N - NAT-traversal, T - cTCP encapsulation     \nX - IKE Extended Authentication, F - IKE Fragmentation\nR - IKE Auto Reconnect, U - IKE Dynamic Route Update\n\nInterface: Tunnel0\nProfile: GRE-IPSEC-PROFILE\nUptime: 04:12:33\nSession status: UP-ACTIVE     \nPeer: 198.51.100.1 port 500 fvrf: (none) ivrf: (none)\n      Phase1_id: 198.51.100.1\n      Desc: (none)\n  Session ID: 0  \n  IKEv2 SA: local 203.0.113.1\/500 remote 198.51.100.1\/500 Active \n          Capabilities:D connid:1 lifetime:19:47:27\n  IPSEC FLOW: permit 47 host 203.0.113.1 host 198.51.100.1 \n        Active SAs: 2, origin: crypto map\n        Inbound:  #pkts decaps: 28455, #pkts decrypt: 28455, #pkts verify: 28455\n        Outbound: #pkts encaps: 31209, #pkts encrypt: 31209, #pkts digest: 31209\n<\/code><\/pre>\n<pre><code class=\"language-ios\">! 2A. Check Phase 1 status if using IKEv2 (Look for Status: READY)\nRouter# show crypto ikev2 sa\n IPv4 Crypto IKEv2  SA \n\nTunnel-id Local                 Remote                fvrf\/ivrf            Status \n1         203.0.113.1\/500       198.51.100.1\/500      none\/none            READY  \n      Encr: AES-CBC, keysize: 256, PRF: SHA512, Hash: SHA512, DH Grp:19, Auth sign: PSK, Auth verify: PSK\n      Life\/Active Time: 86400\/15153 sec\n\n! 2B. Check Phase 1 status if using IKEv1 \/ ISAKMP (Look for state: QM_IDLE)\nRouter# show crypto isakmp sa\nIPv4 Crypto ISAKMP SA\ndst             src             state          conn-id status\n198.51.100.1    203.0.113.1     QM_IDLE           1001 ACTIVE\n<\/code><\/pre>\n<pre><code class=\"language-ios\">! 3. Check Phase 2 IPsec SAs and encryption counters for the specific GRE tunnel\nRouter# show crypto ipsec sa interface tunnel &lt;number&gt;\n\ninterface: Tunnel0\n    Crypto map tag: Tunnel0-head-0, local addr 203.0.113.1\n\n   protected vrf: (none)\n   local  ident (addr\/mask\/prot\/port): (203.0.113.1\/255.255.255.255\/47\/0)\n   remote ident (addr\/mask\/prot\/port): (198.51.100.1\/255.255.255.255\/47\/0)\n   current_peer 198.51.100.1 port 500\n     PERMIT, flags={origin_is_acl,}\n    #pkts encaps: 31209, #pkts encrypt: 31209, #pkts digest: 31209\n    #pkts decaps: 28455, #pkts decrypt: 28455, #pkts verify: 28455\n    #pkts compressed: 0, #pkts decompressed: 0\n    #pkts not compressed: 0, #pkts compr. failed: 0\n    #pkts not decompressed: 0, #pkts decompress failed: 0\n    #send errors 0, #recv errors 0\n\n     local crypto endpt.: 203.0.113.1, remote crypto endpt.: 198.51.100.1\n     path mtu 1500, ip mtu 1500, ip mtu idb GigabitEthernet0\/0\n     current outbound spi: 0xC4901B2A(3297778474)\n     PFS (Y\/N): N, DH group: none\n\n     inbound esp sas:\n      spi: 0x8A3F1104(2319388932)\n        transform: esp-256-aes esp-sha256-hmac ,\n        in use settings ={Tunnel, }\n        conn id: 2001, flow_id: CSR:1, sibling_flagsFFFFFFFF80000048, crypto map: Tunnel0-head-0\n        sa timing: remaining key lifetime (k\/sec): (4607998\/2084)\n        IV size: 16 bytes\n        replay detection support: Y\n        Status: ACTIVE(ACTIVE)\n<\/code><\/pre>\n<p>Key indicators to check in the crypto output:<br \/>\n* <strong><code>Session status: UP-ACTIVE<\/code><\/strong>: Confirms both Phase 1 and Phase 2 negotiations have succeeded for the tunnel.<br \/>\n* <strong><code>IPSEC FLOW: permit 47 host ...<\/code><\/strong>: Verifies that the IPsec transform is explicitly protecting IP Protocol 47 (GRE) between the two tunnel endpoints.<br \/>\n* <strong><code>#pkts encrypt<\/code> and <code>#pkts decrypt<\/code><\/strong>: Repeating the command should show both counters incrementing simultaneously. If <code>#pkts encrypt<\/code> increases while <code>#pkts decrypt<\/code> stays at <code>0<\/code>, return ESP traffic (IP Protocol 50) or UDP port 4500 (NAT-T) is being blocked upstream, or the remote peer&#8217;s tunnel configuration is mismatched.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Step-by-Step_Guide_to_Troubleshooting_Down_or_Flapping_GRE_Tunnels\"><\/span>Step-by-Step Guide to Troubleshooting Down or Flapping GRE Tunnels<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>When your verification checks reveal a tunnel stuck in <code>up\/down<\/code> or constantly bouncing between <code>up<\/code> and <code>down<\/code>, follow this sequential diagnostic workflow to isolate and fix the root cause.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_Query_the_Internal_Tunnel_Line_State_Evaluation_Reason\"><\/span>Step 1: Query the Internal Tunnel Line State Evaluation Reason<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Before testing external paths, check why Cisco IOS marked the tunnel line protocol down using the internal tunnel diagnostic command:<\/p>\n<pre><code class=\"language-ios\">Router# show tunnel interface tunnel &lt;number&gt;\nTunnel0\n   Mode:GRE\/IP, Destination 198.51.100.1, Source GigabitEthernet0\/0\n   Application ID 1: unspecified\n   Tunnel Subblocks:\n      src-track:\n         Tunnel0 source tracking subblock associated with GigabitEthernet0\/0\n         Set of tunnels with source GigabitEthernet0\/0, 1 member (includes iterators), on interface &lt;OK&gt;\n   Linestate - current down\n   Last linestate change time 00:02:14,Reason: Keepalive failed\n<\/code><\/pre>\n<p>Examine the <code>Linestate<\/code> and <code>Reason<\/code> fields (along with the <code>src-track<\/code> subblock). Common reported reasons include <code>Source interface down<\/code>, <code>No route to destination<\/code>, <code>Tunnel destination recursive<\/code>, or <code>Keepalive failed<\/code>. Ensure that the source interface matches an active interface and that both endpoints have matching <code>tunnel source<\/code> and <code>tunnel destination<\/code> declarations (the local source IP must exactly match the remote peer&#8217;s configured destination IP).<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Validate_Underlay_Routing_and_IP_Protocol_47_Reachability\"><\/span>Step 2: Validate Underlay Routing and IP Protocol 47 Reachability<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Verify that the router has a valid underlay route to the remote tunnel destination and that packets can reach it from the exact tunnel source IP:<\/p>\n<pre><code class=\"language-ios\">Router# show ip route 198.51.100.1\nRouting entry for 198.51.100.0\/24\n  Known via &quot;static&quot;, distance 1, metric 0\n  Routing Descriptor Blocks:\n  * 203.0.113.254, via GigabitEthernet0\/0\n      Route metric is 0, traffic share count is 1\n\nRouter# ping 198.51.100.1 source GigabitEthernet0\/0\n<\/code><\/pre>\n<ul>\n<li>If <code>show ip route<\/code> returns <code>% Network not in table<\/code> (and no default route exists), add a static route or verify your underlay IGP\/BGP session.<\/li>\n<li>Remember that a successful ICMP <code>ping<\/code> only confirms ICMP reachability. Intermediate firewalls or router ACLs along the path must explicitly permit <strong>IP Protocol 47 (GRE)<\/strong> (<code>permit gre host &lt;local-ip&gt; host &lt;remote-ip&gt;<\/code>). If an ACL drops Protocol 47, underlay pings will succeed while GRE keepalives and tunnel data fail.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Resolve_Recursive_Routing_Flaps\"><\/span>Step 3: Resolve Recursive Routing Flaps<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If the tunnel interface comes up briefly, drops for a few seconds, and repeats endlessly, inspect the system log (<code>show logging<\/code>):<\/p>\n<pre><code class=\"language-text\">%TUN-5-RECURDOWN: Tunnel0 temporarily disabled due to recursive routing\n%LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to down\n<\/code><\/pre>\n<p><strong>Why this happens<\/strong>: You are running a dynamic routing protocol (such as OSPF, EIGRP, or BGP) over the GRE tunnel, and the remote router is advertising its public\/underlay <code>tunnel destination<\/code> subnet through the tunnel itself. Once the local router learns a better metric or more specific prefix for the tunnel destination <em>via Tunnel0<\/em>, it tries to encapsulate tunnel packets inside Tunnel0, creating a recursion loop that forces IOS to shut down the line protocol.<\/p>\n<p><strong>How to fix it<\/strong>:<br \/>\n1. Add a static <code>\/32<\/code> host route for the remote tunnel destination IP pointing strictly to the physical underlay next-hop gateway (static routes have an Administrative Distance of 1, beating OSPF\/EIGRP\/BGP).<br \/>\n2. Filter the underlay public subnets from being advertised over the GRE tunnel using a <code>distribute-list<\/code>, <code>prefix-list<\/code>, or separate routing protocol autonomous system.<br \/>\n3. Alternatively, place the underlay physical interface into a front-door VRF (FVRF) and bind the tunnel to it using <code>tunnel vrf &lt;vrf-name&gt;<\/code>.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_4_Debug_Keepalive_Drops_and_MTU_Blackholes\"><\/span>Step 4: Debug Keepalive Drops and MTU Blackholes<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If the underlay route is stable but keepalives fail\u2014or the tunnel stays <code>up\/up<\/code> while large TCP sessions stall\u2014use targeted debugs and DF-bit (Don&#8217;t Fragment) pings:<\/p>\n<pre><code class=\"language-ios\">! Monitor GRE keepalive transmission and reception in real time\nRouter# debug tunnel keepalive\nTunnel0: sending keepalive, 203.0.113.1 -&gt; 198.51.100.1 (count=1)\nTunnel0: keepalive received, 198.51.100.1 -&gt; 203.0.113.1\n\n! Turn off debugging immediately after inspection\nRouter# undebug all\n<\/code><\/pre>\n<p>If <code>sending keepalive<\/code> increments <code>count=1<\/code>, <code>count=2<\/code>, <code>count=3<\/code> without a <code>keepalive received<\/code> message, verify whether the remote router has an inbound ACL blocking Protocol 47 or whether asymmetric routing at the remote site is sending the decapsulated return packet out an interface blocked by Unicast Reverse Path Forwarding (uRPF).<\/p>\n<p>Finally, if small pings across the tunnel overlay IP work (<code>ping 10.255.0.2<\/code>), but application traffic hangs, test for MTU fragmentation issues:<\/p>\n<pre><code class=\"language-ios\">Router# ping 10.255.0.2 size 1400 df-bit\n<\/code><\/pre>\n<p>Because GRE adds 24 bytes of overhead (and GRE over IPsec adds 50\u201376+ bytes), configure <code>ip mtu 1400<\/code> and <code>ip tcp adjust-mss 1360<\/code> under the tunnel interface on both routers to prevent mid-stream packet drops.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Automated_Tools_and_SNMP_Methods_for_Monitoring_Cisco_GRE_Tunnels\"><\/span>Automated Tools and SNMP Methods for Monitoring Cisco GRE Tunnels<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Relying on manual CLI checks is impractical when managing dozens of branch sites or DMVPN spokes. Network administrators use automated SNMP polling, active probes, and network management platforms to track GRE tunnel availability continuously:<\/p>\n<ol>\n<li><strong>Standard IF-MIB and Cisco IPsec Flow Monitor MIB Polling (SNMP)<\/strong><br \/>\n   Cisco IOS exposes logical <code>Tunnel<\/code> interfaces in the standard SNMP <code>IF-MIB<\/code> alongside physical ports. Query <code>ifDescr<\/code> (<code>1.3.6.1.2.1.2.2.1.2<\/code>) or <code>ifName<\/code> (<code>1.3.6.1.2.1.31.1.1.1.1<\/code>) to identify the unique <code>ifIndex<\/code> of your <code>TunnelX<\/code> interface, then poll <code>ifOperStatus<\/code> (<code>1.3.6.1.2.1.2.2.1.8.&lt;ifIndex&gt;<\/code>) to monitor its operational state (<code>1<\/code> = up, <code>2<\/code> = down) and <code>ifHCInOctets<\/code> (<code>1.3.6.1.2.1.31.1.1.1.6<\/code>) \/ <code>ifHCOutOctets<\/code> (<code>1.3.6.1.2.1.31.1.1.1.10<\/code>) for 64-bit bandwidth utilization. For GRE over IPsec tunnels, supplement interface polling with <code>CISCO-IPSEC-FLOW-MONITOR-MIB<\/code> (<code>cikeTunStatus<\/code> at <code>1.3.6.1.4.1.9.9.171.1.2.3.1.35<\/code>) to track active IKE Phase 1 sessions.<\/li>\n<li><strong>Cisco IOS IP SLA with Enhanced Object Tracking and EEM<\/strong><br \/>\n   To verify actual overlay data-plane forwarding directly from the router, configure an <code>ip sla<\/code> <code>icmp-echo<\/code> or <code>udp-jitter<\/code> probe targeting the remote tunnel interface IP address (for example, <code>10.255.0.2<\/code>) with a 5-second frequency. Bind the IP SLA operation to a <code>track<\/code> object (<code>track 1 ip sla 1 reachability<\/code>). This generates immediate <code>%TRACK-6-STATE<\/code> syslog events, SNMP traps (<code>CISCO-RTTMON-MIB<\/code>), or Embedded Event Manager (EEM) automated remediation actions whenever overlay traffic fails\u2014even if GRE keepalives are not supported on the remote third-party endpoint.<\/li>\n<li><strong>SolarWinds Network Performance Monitor (NPM)<\/strong><br \/>\n   SolarWinds NPM automatically discovers logical Cisco <code>Tunnel<\/code> interfaces during SNMP node onboarding. It correlates tunnel <code>ifOperStatus<\/code> with dynamic routing neighbor tables (OSPF, EIGRP, and BGP) so operators receive consolidated alerts when a GRE tunnel flaps or drops a routing adjacency, while retaining historical throughput and error counter graphs.<\/li>\n<li><strong>Paessler PRTG Network Monitor<\/strong><br \/>\n   PRTG offers native SNMP Traffic sensors, Cisco IP SLA sensors, and Custom SNMP OID sensors tailored for Cisco routers. Administrators can combine tunnel interface state monitoring with latency and packet-loss thresholds from IP SLA probes to visualize branch-to-hub GRE health on live topology maps.<\/li>\n<li><strong>Zabbix and LibreNMS (Open-Source SNMP &amp; Streaming Telemetry)<\/strong><br \/>\n   Both Zabbix and LibreNMS include built-in Cisco IOS templates that use SNMP Low-Level Discovery (LLD) to automatically detect and monitor <code>Tunnel<\/code> interfaces, alert on <code>ifOperStatus<\/code> changes, and graph interface error counters. On modern Cisco IOS XE platforms, these stacks can also ingest model-driven YANG streaming telemetry (<code>Cisco-IOS-XE-interfaces-oper<\/code>) over gRPC\/NETCONF for sub-second tunnel state visibility without SNMP polling overhead.<\/li>\n<\/ol>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Official_Cisco_IOS_Documentation_and_Command_References_for_GRE\"><\/span>Official Cisco IOS Documentation and Command References for GRE<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>For platform-specific syntax, hardware scaling limits, and RFC compliance details, consult the primary Cisco technical publications below:<\/p>\n<ul>\n<li><strong>Cisco IOS XE Interface and Hardware Component Configuration Guide \u2014 Module: <em>Implementing Tunnels<\/em><\/strong><br \/>\n  Defines the architectural specifications, prerequisites, and configuration procedures for point-to-point GRE over IPv4\/IPv6, multipoint GRE (mGRE), Path MTU Discovery (<code>tunnel path-mtu-discovery<\/code>), and GRE tunnel key\/checksum options.<\/li>\n<li><strong>Cisco IOS Interface and Hardware Component Command Reference \u2014 <em>I through K<em> and <\/em>S through Z<\/em><\/strong><br \/>\n  Provides the authoritative syntax definitions, default values, and usage guidelines for <code>interface tunnel<\/code>, <code>tunnel source<\/code>, <code>tunnel destination<\/code>, <code>tunnel mode gre<\/code>, <code>keepalive<\/code>, <code>show interfaces tunnel<\/code>, and <code>debug tunnel<\/code>.<\/li>\n<li><strong>Cisco Support Technical Note \u2014 <em>Resolve GRE Tunnel Interface States<\/em> (Document ID: 118850)<\/strong><br \/>\n  Specifies the exact internal evaluation rules for point-to-point GRE and mGRE line protocol states, details <code>src-track<\/code> subblock tracking dependencies (including HSRP VIP redundancy states), and documents the <code>show tunnel interface tunnel &lt;number&gt;<\/code> diagnostic command.<\/li>\n<li><strong>Cisco Support Technical Note \u2014 <em>Understand GRE Tunnel Keepalives<\/em><\/strong><br \/>\n  Documents the packet construction of GRE keepalive probes, explains why one-way keepalive configuration functions with remote routers that do not configure keepalives, and outlines firewall ACL considerations for IP Protocol 47.<\/li>\n<li><strong>Cisco IOS XE Security Configuration Guide: Secure Connectivity \u2014 Module: <em>GRE Tunnel IPsec Protection<\/em><\/strong><br \/>\n  Details the configuration and verification of virtual tunnel interface protection using <code>tunnel protection ipsec profile<\/code>, IKEv1\/IKEv2 profiles, and <code>show crypto session<\/code> diagnostic outputs.<\/li>\n<\/ul>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span>Conclusion<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Checking GRE tunnel status on a Cisco router starts with <code>show ip interface brief<\/code> and <code>show interfaces tunnel &lt;number&gt;<\/code>, but accurate verification goes beyond confirming an <code>up\/up<\/code> status line. Because GRE is inherently stateless, enabling <code>keepalive<\/code> on the tunnel interface\u2014and verifying Phase 1 and Phase 2 crypto sessions with <code>show crypto session detail<\/code> when using IPsec\u2014ensures the CLI reflects real end-to-end reachability. Combined with underlay route validation to prevent recursive routing flaps and SNMP or IP SLA monitoring for automated alerting, these practices keep your Cisco GRE overlay links predictable and resilient.<\/p>\n<div class='sfsi_Sicons' style='width: 100%; display: inline-block; vertical-align: middle; text-align:left'><div style='margin:0px 8px 0px 0px; line-height: 24px'><span>Please follow and like us:<\/span><\/div><div class='sfsi_socialwpr'><div class='sf_fb_share sf_icon' style='text-align:left;vertical-align: middle;'><a href='https:\/\/www.facebook.com\/sharer\/sharer.php?u=https%3A%2F%2Fcciedump.spoto.net%2Fblog%2Fhow-to-check-gre-tunnel-status-in-cisco-router_24580.html' style='display:inline-block;'  > <img class='sfsi_wicon'  data-pin-nopin='true' width='auto' height='auto' alt='fb-share-icon' title='Facebook Share' src='https:\/\/cciedump.spoto.net\/blog\/wp-content\/plugins\/ultimate-social-media-icons\/images\/visit_icons\/fbshare_bck.png'  \/><\/a><\/div><div class='sf_twiter sf_icon' style='display: inline-block;vertical-align: middle;width: auto;margin-left: 7px;'>\r\n\t\t\t\t\t\t<a target='_blank' href='https:\/\/twitter.com\/intent\/tweet?text=How+to+Check+GRE+Tunnel+Status+in+Cisco+Router+https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html'style='display:inline-block' >\r\n\t\t\t\t\t\t\t<img data-pin-nopin= true width='auto' class='sfsi_wicon' src='https:\/\/cciedump.spoto.net\/blog\/wp-content\/plugins\/ultimate-social-media-icons\/images\/visit_icons\/en_US_Tweet.svg' alt='Tweet' title='Tweet' >\r\n\t\t\t\t\t\t<\/a>\r\n\t\t\t\t\t<\/div><div class='sf_pinit sf_icon' style='text-align:left;vertical-align: middle;float:left;line-height: 33px;width:auto;margin: 0 -2px;'><a href='#'  onclick='sfsi_pinterest_modal_images(event,\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\",\"How to Check GRE Tunnel Status in Cisco Router\")' style='display:inline-block;'  > <img class='sfsi_wicon'  data-pin-nopin='true' width='auto' height='auto' alt='fb-share-icon' title='Pin Share' src='https:\/\/cciedump.spoto.net\/blog\/wp-content\/plugins\/ultimate-social-media-icons\/images\/share_icons\/Pinterest_Save\/en_US_save.svg'  \/><\/a><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"<p>Generic Routing Encapsulation (GRE) tunnels provide virtual point-to-point and multipoint connectivity across IP networks, enabling Cisco routers to transport routing protocols, multicast streams, and IPv6 payloads over an existing IPv4 or IPv6 underlay. Because a GRE tunnel is a logical construct rather than a physical wire, verifying whether it is truly operational requires checking more&#8230; &raquo; <a class=\"read-more-link\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\">read more<\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3,608],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v18.0 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>How to Check GRE Tunnel Status in Cisco Router - SPOTO Official Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Check GRE Tunnel Status in Cisco Router - SPOTO Official Blog\" \/>\n<meta property=\"og:description\" content=\"Generic Routing Encapsulation (GRE) tunnels provide virtual point-to-point and multipoint connectivity across IP networks, enabling Cisco routers to transport routing protocols, multicast streams, and IPv6 payloads over an existing IPv4 or IPv6 underlay. Because a GRE tunnel is a logical construct rather than a physical wire, verifying whether it is truly operational requires checking more... &raquo; read more\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\" \/>\n<meta property=\"og:site_name\" content=\"SPOTO Official Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-17T07:22:16+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"SPOTO \u7f16\u8f91\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"14 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638\",\"name\":\"SPOTO Club\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg\",\"contentUrl\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg\",\"caption\":\"SPOTO Club\"},\"logo\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#personlogo\"},\"description\":\"SPOTO is an excellent leader in IT certification training for 20+ years. We offer 100% real Cisco CCNA, CCNP exam dumps, CCIE Lab study materials, PMP, CISA, CISM, AWS, Palo Alto, and other IT exam dumps. We have helped thousands of candidates around the world to pass their IT exams on the first try! As the first-class online IT training organization in China, SPOTO cooperates with many giant Internet companies in China like Tencent, Baidu, and Alibaba. What\u2019s more, we have won lots of awards in IT education training such as \u201cTop Ten Influential Brands In Online Education Industry\u201d given by Baidu, \u201cOfficial IT Online Training Organization\u201d awarded by Tencent Class, etc. Join us: https:\/\/cciedump.spoto.net\/ Contact us: E-mail: support@spoto.net Phone \/ WhatsApp: +86 18344981205\",\"sameAs\":[\"https:\/\/cciedump.spoto.net\/\"]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#website\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/\",\"name\":\"SPOTO Official Blog\",\"description\":\"Focus on Online IT Training for 20+ Years\",\"publisher\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/cciedump.spoto.net\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#webpage\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\",\"name\":\"How to Check GRE Tunnel Status in Cisco Router - SPOTO Official Blog\",\"isPartOf\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#website\"},\"datePublished\":\"2026-11-17T07:22:16+00:00\",\"dateModified\":\"2026-11-17T07:22:16+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/cciedump.spoto.net\/blog\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Check GRE Tunnel Status in Cisco Router\"}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#article\",\"isPartOf\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#webpage\"},\"author\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1\"},\"headline\":\"How to Check GRE Tunnel Status in Cisco Router\",\"datePublished\":\"2026-11-17T07:22:16+00:00\",\"dateModified\":\"2026-11-17T07:22:16+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#webpage\"},\"wordCount\":1895,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638\"},\"articleSection\":[\"CCNA Certification\",\"Cisco Certification\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#respond\"]}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1\",\"name\":\"SPOTO \u7f16\u8f91\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155\",\"contentUrl\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155\",\"caption\":\"SPOTO \u7f16\u8f91\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Check GRE Tunnel Status in Cisco Router - SPOTO Official Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html","og_locale":"en_US","og_type":"article","og_title":"How to Check GRE Tunnel Status in Cisco Router - SPOTO Official Blog","og_description":"Generic Routing Encapsulation (GRE) tunnels provide virtual point-to-point and multipoint connectivity across IP networks, enabling Cisco routers to transport routing protocols, multicast streams, and IPv6 payloads over an existing IPv4 or IPv6 underlay. Because a GRE tunnel is a logical construct rather than a physical wire, verifying whether it is truly operational requires checking more... &raquo; read more","og_url":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html","og_site_name":"SPOTO Official Blog","article_published_time":"2026-11-17T07:22:16+00:00","twitter_card":"summary_large_image","twitter_misc":{"Written by":"SPOTO \u7f16\u8f91","Est. reading time":"14 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":["Person","Organization"],"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638","name":"SPOTO Club","image":{"@type":"ImageObject","@id":"https:\/\/cciedump.spoto.net\/blog\/#personlogo","inLanguage":"en-US","url":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg","contentUrl":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg","caption":"SPOTO Club"},"logo":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#personlogo"},"description":"SPOTO is an excellent leader in IT certification training for 20+ years. We offer 100% real Cisco CCNA, CCNP exam dumps, CCIE Lab study materials, PMP, CISA, CISM, AWS, Palo Alto, and other IT exam dumps. We have helped thousands of candidates around the world to pass their IT exams on the first try! As the first-class online IT training organization in China, SPOTO cooperates with many giant Internet companies in China like Tencent, Baidu, and Alibaba. What\u2019s more, we have won lots of awards in IT education training such as \u201cTop Ten Influential Brands In Online Education Industry\u201d given by Baidu, \u201cOfficial IT Online Training Organization\u201d awarded by Tencent Class, etc. Join us: https:\/\/cciedump.spoto.net\/ Contact us: E-mail: support@spoto.net Phone \/ WhatsApp: +86 18344981205","sameAs":["https:\/\/cciedump.spoto.net\/"]},{"@type":"WebSite","@id":"https:\/\/cciedump.spoto.net\/blog\/#website","url":"https:\/\/cciedump.spoto.net\/blog\/","name":"SPOTO Official Blog","description":"Focus on Online IT Training for 20+ Years","publisher":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cciedump.spoto.net\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#webpage","url":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html","name":"How to Check GRE Tunnel Status in Cisco Router - SPOTO Official Blog","isPartOf":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#website"},"datePublished":"2026-11-17T07:22:16+00:00","dateModified":"2026-11-17T07:22:16+00:00","breadcrumb":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cciedump.spoto.net\/blog"},{"@type":"ListItem","position":2,"name":"How to Check GRE Tunnel Status in Cisco Router"}]},{"@type":"Article","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#article","isPartOf":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#webpage"},"author":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1"},"headline":"How to Check GRE Tunnel Status in Cisco Router","datePublished":"2026-11-17T07:22:16+00:00","dateModified":"2026-11-17T07:22:16+00:00","mainEntityOfPage":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#webpage"},"wordCount":1895,"commentCount":0,"publisher":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638"},"articleSection":["CCNA Certification","Cisco Certification"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/cciedump.spoto.net\/blog\/how-to-check-gre-tunnel-status-in-cisco-router_24580.html#respond"]}]},{"@type":"Person","@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1","name":"SPOTO \u7f16\u8f91","image":{"@type":"ImageObject","@id":"https:\/\/cciedump.spoto.net\/blog\/#personlogo","inLanguage":"en-US","url":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155","contentUrl":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155","caption":"SPOTO \u7f16\u8f91"}}]}},"_links":{"self":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/posts\/24580"}],"collection":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/comments?post=24580"}],"version-history":[{"count":0,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/posts\/24580\/revisions"}],"wp:attachment":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/media?parent=24580"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/categories?post=24580"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/tags?post=24580"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}