{"id":24594,"date":"2026-11-17T17:10:14","date_gmt":"2026-11-17T09:10:14","guid":{"rendered":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html"},"modified":"2026-11-17T17:10:14","modified_gmt":"2026-11-17T09:10:14","slug":"how-to-check-ospf-status-on-cisco-router","status":"publish","type":"post","link":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html","title":{"rendered":"How to Check OSPF Status on Cisco Router"},"content":{"rendered":"<p>Verifying Open Shortest Path First (OSPF) operational health on a Cisco router requires more than checking whether a neighbor appears in a list. Because OSPF is a link-state routing protocol, a healthy deployment depends on four distinct layers working together: an active local OSPF process, properly bound interfaces, synchronized neighbor adjacencies, and a consistent Link-State Database (LSDB) that successfully installs paths into the IP routing table. Whether you are performing a routine network audit, validating a maintenance window, or isolating a routing outage, following a structured command-line workflow ensures you catch subtle configuration mismatches before they cause blackholed traffic.<\/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-ospf-status-on-cisco-router_24594.html\/#Core_CLI_Commands_to_Verify_OSPF_Processes_Interfaces_and_Neighbors\" title=\"Core CLI Commands to Verify OSPF Processes, Interfaces, and Neighbors\">Core CLI Commands to Verify OSPF Processes, Interfaces, and Neighbors<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Step_1_Verify_the_Global_OSPF_Process_and_Router_ID\" title=\"Step 1: Verify the Global OSPF Process and Router ID\">Step 1: Verify the Global OSPF Process and Router ID<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Step_2_Check_OSPF-Enabled_Interfaces\" title=\"Step 2: Check OSPF-Enabled Interfaces\">Step 2: Check OSPF-Enabled Interfaces<\/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-ospf-status-on-cisco-router_24594.html\/#Step_3_Verify_OSPF_Neighbor_Adjacencies\" title=\"Step 3: Verify OSPF Neighbor Adjacencies\">Step 3: Verify OSPF Neighbor Adjacencies<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Understanding_OSPF_Neighbor_States_and_DRBDR_Roles\" title=\"Understanding OSPF Neighbor States and DR\/BDR Roles\">Understanding OSPF Neighbor States and DR\/BDR Roles<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#OSPF_Neighbor_Adjacency_States_Compared\" title=\"OSPF Neighbor Adjacency States Compared\">OSPF Neighbor Adjacency States Compared<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Designated_Router_DRBDR_Role_Combinations_Explained\" title=\"Designated Router (DR\/BDR) Role Combinations Explained\">Designated Router (DR\/BDR) Role Combinations Explained<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#How_to_Check_the_OSPF_Link-State_Database_LSDB_and_Routing_Table\" title=\"How to Check the OSPF Link-State Database (LSDB) and Routing Table\">How to Check the OSPF Link-State Database (LSDB) and Routing Table<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Step_1_Inspect_the_Link-State_Database_Summary\" title=\"Step 1: Inspect the Link-State Database Summary\">Step 1: Inspect the Link-State Database Summary<\/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-ospf-status-on-cisco-router_24594.html\/#Step_2_Drill_Down_into_Specific_LSAs\" title=\"Step 2: Drill Down into Specific LSAs\">Step 2: Drill Down into Specific LSAs<\/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-ospf-status-on-cisco-router_24594.html\/#Step_3_Verify_OSPF_Routes_in_the_Cisco_Routing_Table\" title=\"Step 3: Verify OSPF Routes in the Cisco Routing Table\">Step 3: Verify OSPF Routes in the Cisco Routing Table<\/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-ospf-status-on-cisco-router_24594.html\/#Troubleshooting_Missing_or_Stuck_OSPF_Neighbors_FAQ\" title=\"Troubleshooting Missing or Stuck OSPF Neighbors (FAQ)\">Troubleshooting Missing or Stuck OSPF Neighbors (FAQ)<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Why_is_my_OSPF_neighbor_completely_missing_from_show_ip_ospf_neighbor\" title=\"Why is my OSPF neighbor completely missing from show ip ospf neighbor?\">Why is my OSPF neighbor completely missing from show ip ospf neighbor?<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Why_is_an_OSPF_neighbor_stuck_in_the_INIT_state\" title=\"Why is an OSPF neighbor stuck in the INIT state?\">Why is an OSPF neighbor stuck in the INIT state?<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Why_is_an_OSPF_neighbor_stuck_in_EXSTART_or_EXCHANGE\" title=\"Why is an OSPF neighbor stuck in EXSTART or EXCHANGE?\">Why is an OSPF neighbor stuck in EXSTART or EXCHANGE?<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Why_do_neighbors_reach_FULL_state_but_OSPF_routes_are_missing_from_show_ip_route_ospf\" title=\"Why do neighbors reach FULL state, but OSPF routes are missing from show ip route ospf?\">Why do neighbors reach FULL state, but OSPF routes are missing from show ip route ospf?<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#How_do_I_safely_run_debug_ip_ospf_commands_on_a_production_router\" title=\"How do I safely run debug ip ospf commands on a production router?\">How do I safely run debug ip ospf commands on a production router?<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Cisco_Router_OSPF_Verification_and_Audit_CLI_Cheat_Sheet_Template\" title=\"Cisco Router OSPF Verification and Audit CLI Cheat Sheet Template\">Cisco Router OSPF Verification and Audit CLI Cheat Sheet Template<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-19\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Cisco_IOS_OSPF_Command_Reference_and_Documentation_Specifications\" title=\"Cisco IOS OSPF Command Reference and Documentation Specifications\">Cisco IOS OSPF Command Reference and Documentation Specifications<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-20\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Formal_Command_Syntax_and_Modes\" title=\"Formal Command Syntax and Modes\">Formal Command Syntax and Modes<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-21\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#OS_Version_and_Platform_Compatibility_Matrix\" title=\"OS Version and Platform Compatibility Matrix\">OS Version and Platform Compatibility Matrix<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-22\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Official_Cisco_Documentation_Portal_References\" title=\"Official Cisco Documentation Portal References\">Official Cisco Documentation Portal References<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-23\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\/#Conclusion\" title=\"Conclusion\">Conclusion<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Core_CLI_Commands_to_Verify_OSPF_Processes_Interfaces_and_Neighbors\"><\/span>Core CLI Commands to Verify OSPF Processes, Interfaces, and Neighbors<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>To check OSPF status systematically on a Cisco IOS or IOS XE router, start at the local process level and work outward toward your active interfaces and directly connected neighbors. Follow this three-step verification sequence in Privileged EXEC mode (<code>#<\/code>).<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_Verify_the_Global_OSPF_Process_and_Router_ID\"><\/span>Step 1: Verify the Global OSPF Process and Router ID<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Before checking individual links, confirm that the OSPF routing process is running and using the expected Router ID (RID).<\/p>\n<pre><code class=\"language-ios\">Router# show ip ospf\n Routing Process &quot;ospf 1&quot; with ID 10.255.255.1\n Start time: 00:02:14.112, Time elapsed: 4d12h\n Supports only single TOS(TOS0) routes\n Supports opaque LSA\n Supports Link-local Signaling (LLS)\n Supports area transit capability\n Event-log enabled, Maximum number of events: 1000, Mode: cyclic\n It is an area border router\n Router is not originating router-LSAs with maximum metric\n Initial SPF schedule delay 5000 msecs\n Minimum hold time between two consecutive SPFs 10000 msecs\n Maximum wait time between two consecutive SPFs 10000 msecs\n Auto-cost reference bandwidth unit is 100000 Mbps\n    Area BACKBONE(0)\n        Number of interfaces in this area is 2 (1 loopback)\n        Area has no authentication\n        SPF algorithm last executed 04:11:22.104 ago\n        SPF algorithm executed 7 times\n<\/code><\/pre>\n<p><strong>What to inspect:<\/strong><br \/>\n* <strong>Process ID and Router ID:<\/strong> Appears in the first line (<code>Routing Process \"ospf 1\" with ID 10.255.255.1<\/code>). If the Router ID changed recently, OSPF must be cleared or reloaded for the new ID to take effect.<br \/>\n* <strong>Router Role:<\/strong> Indicates whether the device is an Area Border Router (<code>ABR<\/code>) or Autonomous System Boundary Router (<code>ASBR<\/code>).<br \/>\n* <strong>Reference Bandwidth:<\/strong> Verify <code>Auto-cost reference bandwidth<\/code> matches across all routers in the domain so path costs are calculated consistently.<br \/>\n* <strong>SPF Execution Count:<\/strong> A rapidly climbing <code>SPF algorithm executed<\/code> counter coupled with a very recent timestamp indicates a flapping link inside the area.<\/p>\n<p><em>(Tip: You can also run <code>show ip protocols<\/code> to see which <code>network<\/code> statements, passive interfaces, and route filters are applied to the OSPF process.)<\/em><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Check_OSPF-Enabled_Interfaces\"><\/span>Step 2: Check OSPF-Enabled Interfaces<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Next, verify which interfaces are actively participating in OSPF, which area they belong to, and how many neighbors are forming adjacencies on each link.<\/p>\n<pre><code class=\"language-ios\">Router# show ip ospf interface brief\nInterface    PID   Area            IP Address\/Mask    Cost  State Nbrs F\/C\nLo0          1     0               10.255.255.1\/32    1     LOOP  0\/0\nGi0\/0        1     0               10.1.12.1\/30       10    P2P   1\/1\nGi0\/1        1     0               172.16.10.1\/24     10    DR    3\/3\n<\/code><\/pre>\n<p><strong>What to inspect:<\/strong><br \/>\n* <strong>State:<\/strong> Shows the operational OSPF interface state (<code>LOOP<\/code> for loopback, <code>P2P<\/code> for point-to-point, <code>DR<\/code>, <code>BDR<\/code>, or <code>DROTHER<\/code> for broadcast\/non-broadcast multi-access links, and <code>WAITING<\/code> if the router is still in the DR\/BDR election timer window).<br \/>\n* <strong>Nbrs F\/C:<\/strong> Displays the ratio of <strong>Full<\/strong> (<code>F<\/code>) adjacencies to the total <strong>Count<\/strong> (<code>C<\/code>) of discovered neighbors on that interface. For example, <code>3\/3<\/code> means three neighbors are discovered and all three are fully adjacent.<\/p>\n<p>If you need to inspect timer intervals, network types, or authentication settings on a specific port, drill down with the full interface command:<\/p>\n<pre><code class=\"language-ios\">Router# show ip ospf interface GigabitEthernet0\/0\nGigabitEthernet0\/0 is up, line protocol is up \n  Internet Address 10.1.12.1\/30, Area 0, Attached via Network Statement\n  Process ID 1, Router ID 10.255.255.1, Network Type POINT_TO_POINT, Cost: 10\n  Topology-MTID    Cost    Disabled    Shutdown      Topology Name\n        0           10        no          no            Base\n  Transmit Delay is 1 sec, State POINT_TO_POINT\n  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5\n  Simple password authentication enabled\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Verify_OSPF_Neighbor_Adjacencies\"><\/span>Step 3: Verify OSPF Neighbor Adjacencies<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Finally, check the neighbor table to confirm that adjacent routers have discovered one another and synchronized their databases.<\/p>\n<pre><code class=\"language-ios\">Router# show ip ospf neighbor\n\nNeighbor ID     Pri   State           Dead Time   Address         Interface\n10.255.255.2      0   FULL\/  -        00:00:36    10.1.12.2       GigabitEthernet0\/0\n10.255.255.3      1   FULL\/BDR        00:00:33    172.16.10.2     GigabitEthernet0\/1\n10.255.255.4      1   FULL\/DROTHER    00:00:38    172.16.10.3     GigabitEthernet0\/1\n10.255.255.5      0   2WAY\/DROTHER    00:00:35    172.16.10.4     GigabitEthernet0\/1\n<\/code><\/pre>\n<p><strong>What to inspect:<\/strong><br \/>\n* <strong>Neighbor ID:<\/strong> The OSPF Router ID of the remote neighbor (not necessarily the IP address of the connected interface).<br \/>\n* <strong>Pri:<\/strong> The neighbor&#8217;s OSPF interface priority (<code>0<\/code> to <code>255<\/code>). A priority of <code>0<\/code> means the neighbor will never participate as a Designated Router (DR) or Backup Designated Router (BDR).<br \/>\n* <strong>Dead Time:<\/strong> Counts down from the configured Dead interval (default <code>40<\/code> seconds on broadcast\/point-to-point links) and resets every time a valid Hello packet arrives. If it drops below <code>00:00:30<\/code> on a default link, Hello packets are being dropped or delayed.<\/p>\n<p><strong>Key Takeaway:<\/strong> Always progress from <code>show ip ospf<\/code> to <code>show ip ospf interface brief<\/code> and then <code>show ip ospf neighbor<\/code> so you can immediately tell whether an issue lies with the local router process, an interface binding, or the remote peer.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Understanding_OSPF_Neighbor_States_and_DRBDR_Roles\"><\/span>Understanding OSPF Neighbor States and DR\/BDR Roles<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>When reviewing the <code>State<\/code> column in <code>show ip ospf neighbor<\/code> output (as shown in Step 3 above), OSPF reports both the adjacency state machine phase and the neighbor&#8217;s Designated Router role separated by a slash (for example, <code>FULL\/DR<\/code> or <code>2WAY\/DROTHER<\/code>).<\/p>\n<h3><span class=\"ez-toc-section\" id=\"OSPF_Neighbor_Adjacency_States_Compared\"><\/span>OSPF Neighbor Adjacency States Compared<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>The table below compares all eight OSPF neighbor states in chronological order of adjacency formation, explaining whether each state is normal during steady-state operations and what causes a neighbor to freeze in that phase.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">OSPF State<\/th>\n<th style=\"text-align: left;\">Protocol Phase \/ What Is Happening<\/th>\n<th style=\"text-align: left;\">Normal in Steady State?<\/th>\n<th style=\"text-align: left;\">Primary Cause if Stuck<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>Down<\/strong><\/td>\n<td style=\"text-align: left;\">No OSPF Hello packets have been received from the neighbor within the Dead interval.<\/td>\n<td style=\"text-align: left;\">No (Usually removed from table unless statically configured)<\/td>\n<td style=\"text-align: left;\">Physical link down, OSPF not enabled on remote interface, or IP subnet mismatch.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Attempt<\/strong><\/td>\n<td style=\"text-align: left;\">Unicast Hellos are being sent to a manually configured <code>neighbor<\/code> on an NBMA network, waiting for a reply.<\/td>\n<td style=\"text-align: left;\">No<\/td>\n<td style=\"text-align: left;\">NBMA Frame-Relay\/DMVPN mapping error or wrong neighbor IP address configured.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Init<\/strong><\/td>\n<td style=\"text-align: left;\">Local router received a Hello packet from the neighbor, but the local router&#8217;s own Router ID is not listed inside that Hello packet.<\/td>\n<td style=\"text-align: left;\">No<\/td>\n<td style=\"text-align: left;\">Unidirectional link, ACL or firewall blocking multicast <code>224.0.0.5<\/code> in one direction, or Layer 2 loop\/filtering.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>2-Way<\/strong><\/td>\n<td style=\"text-align: left;\">Bidirectional communication is established; both routers see their own Router ID inside the neighbor&#8217;s Hello packet. DR\/BDR election occurs here.<\/td>\n<td style=\"text-align: left;\"><strong>Yes<\/strong>, but <em>only<\/em> between two <code>DROTHER<\/code> routers on a broadcast\/NBMA segment<\/td>\n<td style=\"text-align: left;\">Normal for <code>DROTHER<\/code>-to-<code>DROTHER<\/code> peers; if stuck here between all peers on a segment, all routers have OSPF priority set to <code>0<\/code>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>ExStart<\/strong><\/td>\n<td style=\"text-align: left;\">Routers negotiate Master\/Slave roles (highest Router ID wins) and initial Database Description (DBD) sequence numbers.<\/td>\n<td style=\"text-align: left;\">No<\/td>\n<td style=\"text-align: left;\">Interface <strong>MTU mismatch<\/strong> between neighbors or duplicate OSPF Router IDs.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Exchange<\/strong><\/td>\n<td style=\"text-align: left;\">Routers exchange DBD packets containing LSA headers to compare their Link-State Databases.<\/td>\n<td style=\"text-align: left;\">No<\/td>\n<td style=\"text-align: left;\">Interface MTU mismatch (large DBD frames dropped) or corrupted packets in transit.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Loading<\/strong><\/td>\n<td style=\"text-align: left;\">Routers send Link-State Request (LSR) packets for missing or newer LSAs and respond with Link-State Update (LSU) packets.<\/td>\n<td style=\"text-align: left;\">No<\/td>\n<td style=\"text-align: left;\">Corrupted LSA, memory exhaustion, or MTU\/fragmentation issues dropping large LSU packets.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Full<\/strong><\/td>\n<td style=\"text-align: left;\">Both routers have identical Link-State Databases for the shared area and exchange Link-State Acknowledgments (LSAck).<\/td>\n<td style=\"text-align: left;\"><strong>Yes<\/strong> (Target state for all P2P links and all DR\/BDR relationships)<\/td>\n<td style=\"text-align: left;\">N\/A \u2014 Adjacency is healthy and complete.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><span class=\"ez-toc-section\" id=\"Designated_Router_DRBDR_Role_Combinations_Explained\"><\/span>Designated Router (DR\/BDR) Role Combinations Explained<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>The value after the slash in the <code>State<\/code> column identifies the neighbor&#8217;s role on the shared network segment:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Output String<\/th>\n<th style=\"text-align: left;\">Network Type<\/th>\n<th style=\"text-align: left;\">Neighbor Role<\/th>\n<th style=\"text-align: left;\">Expected Behavior<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong><code>FULL\/DR<\/code><\/strong><\/td>\n<td style=\"text-align: left;\">Broadcast \/ NBMA<\/td>\n<td style=\"text-align: left;\">Designated Router<\/td>\n<td style=\"text-align: left;\">Neighbor is the elected DR for the segment. All routers on the subnet form a <code>FULL<\/code> adjacency with the DR.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong><code>FULL\/BDR<\/code><\/strong><\/td>\n<td style=\"text-align: left;\">Broadcast \/ NBMA<\/td>\n<td style=\"text-align: left;\">Backup Designated Router<\/td>\n<td style=\"text-align: left;\">Neighbor is the elected BDR. All routers on the subnet also form a <code>FULL<\/code> adjacency with the BDR.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong><code>FULL\/DROTHER<\/code><\/strong><\/td>\n<td style=\"text-align: left;\">Broadcast \/ NBMA<\/td>\n<td style=\"text-align: left;\">Non-DR \/ Non-BDR Router<\/td>\n<td style=\"text-align: left;\">Neighbor is neither the DR nor the BDR, <strong>and<\/strong> your local router <em>is<\/em> the DR or BDR (hence the <code>FULL<\/code> state).<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong><code>2WAY\/DROTHER<\/code><\/strong><\/td>\n<td style=\"text-align: left;\">Broadcast \/ NBMA<\/td>\n<td style=\"text-align: left;\">Non-DR \/ Non-BDR Router<\/td>\n<td style=\"text-align: left;\"><strong>Completely normal.<\/strong> Both your local router and the neighbor are <code>DROTHER<\/code> routers. To reduce LSA flooding overhead, <code>DROTHER<\/code> peers stay in <code>2WAY<\/code> with each other and only exchange LSAs via the DR and BDR.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong><code>FULL\/ -<\/code><\/strong><\/td>\n<td style=\"text-align: left;\">Point-to-Point \/ Point-to-Multipoint<\/td>\n<td style=\"text-align: left;\">No DR\/BDR Election<\/td>\n<td style=\"text-align: left;\">The hyphen (<code>-<\/code>) indicates an OSPF network type where no DR or BDR election takes place; routers form a direct <code>FULL<\/code> adjacency.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Key Takeaway:<\/strong> Seeing <code>FULL<\/code> is always healthy, and seeing <code>2WAY\/DROTHER<\/code> is completely normal on multi-access Ethernet segments whenever neither router is the elected DR or BDR.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"How_to_Check_the_OSPF_Link-State_Database_LSDB_and_Routing_Table\"><\/span>How to Check the OSPF Link-State Database (LSDB) and Routing Table<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Even when neighbors reach the <code>FULL<\/code> state, topological mismatches or route filtering can prevent OSPF routes from entering the Global Routing Information Base (RIB). Follow this progression to verify that Link-State Advertisements (LSAs) are present in the database and installed as active IP routes.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_Inspect_the_Link-State_Database_Summary\"><\/span>Step 1: Inspect the Link-State Database Summary<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Run <code>show ip ospf database<\/code> to view a summary of all LSAs stored in the router&#8217;s LSDB, grouped by Area and LSA Type.<\/p>\n<pre><code class=\"language-ios\">Router# show ip ospf database\n\n            OSPF Router with ID (10.255.255.1) (Process ID 1)\n\n                Router Link States (Area 0)\n\nLink ID         ADV Router      Age         Seq#       Checksum Link count\n10.255.255.1    10.255.255.1    412         0x80000014 0x004A12 3\n10.255.255.2    10.255.255.2    398         0x80000011 0x009B31 2\n\n                Net Link States (Area 0)\n\nLink ID         ADV Router      Age         Seq#       Checksum\n172.16.10.2     10.255.255.3    405         0x80000009 0x00C210\n\n                Summary Net Link States (Area 0)\n\nLink ID         ADV Router      Age         Seq#       Checksum\n192.168.20.0    10.255.255.2    1120        0x80000005 0x007E44\n\n                Type-5 AS External Link States\n\nLink ID         ADV Router      Age         Seq#       Checksum Tag\n10.100.0.0      10.255.255.4    85          0x80000002 0x001F88 0\n<\/code><\/pre>\n<p><strong>How to read the database categories:<\/strong><br \/>\n* <strong>Router Link States (Type 1 LSA):<\/strong> Generated by every router inside an area; lists connected links and costs (<code>Link ID<\/code> = originating Router ID).<br \/>\n* <strong>Net Link States (Type 2 LSA):<\/strong> Generated by the DR on broadcast\/NBMA segments (<code>Link ID<\/code> = IP address of the DR&#8217;s interface).<br \/>\n* <strong>Summary Net Link States (Type 3 LSA):<\/strong> Generated by ABRs to advertise inter-area prefixes (<code>Link ID<\/code> = destination subnet).<br \/>\n* <strong>Summary ASB Link States (Type 4 LSA):<\/strong> Generated by ABRs to advertise the reachability of an ASBR (<code>Link ID<\/code> = ASBR Router ID).<br \/>\n* <strong>Type-5 AS External Link States (Type 5 LSA):<\/strong> Generated by ASBRs for redistributed external routes across the OSPF domain.<br \/>\n* <strong>NSSA External Link States (Type 7 LSA):<\/strong> Generated by ASBRs inside a Not-So-Stubby Area (NSSA).<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Drill_Down_into_Specific_LSAs\"><\/span>Step 2: Drill Down into Specific LSAs<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If a specific prefix is missing from the routing table, inspect the detailed LSA payload to verify its advertising router, subnet mask, metric, and forwarding address:<\/p>\n<pre><code class=\"language-ios\">! Inspect all Type 1 Router LSAs or filter by a specific originating Router ID\nRouter# show ip ospf database router 10.255.255.2\n\n! Inspect a specific Type 3 Inter-Area Summary LSA\nRouter# show ip ospf database summary 192.168.20.0\n\n! Inspect all LSAs originated locally by this router\nRouter# show ip ospf database self-originate\n<\/code><\/pre>\n<p>Checking <code>Age<\/code> is also critical during verification: normal LSA age increments from <code>0<\/code> up to <code>1800<\/code> seconds (30 minutes) before refreshing. If an LSA&#8217;s age is stuck at <code>3600<\/code> (<code>MAXAGE<\/code>), the originating router is purging that route from the OSPF domain.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Verify_OSPF_Routes_in_the_Cisco_Routing_Table\"><\/span>Step 3: Verify OSPF Routes in the Cisco Routing Table<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Once you confirm the LSAs exist in the database, verify that the Shortest Path First (SPF) algorithm calculated valid paths and installed them into the IP routing table:<\/p>\n<pre><code class=\"language-ios\">Router# show ip route ospf\nCodes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP\n       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area \n       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2\n       E1 - OSPF external type 1, E2 - OSPF external type 2\n       * - candidate default, U - per-user static route, o - ODR\n\n      10.0.0.0\/8 is variably subnetted, 5 subnets, 2 masks\nO        10.255.255.2\/32 [110\/11] via 10.1.12.2, 04:11:20, GigabitEthernet0\/0\nO E2     10.100.0.0\/16 [110\/20] via 172.16.10.3, 00:01:25, GigabitEthernet0\/1\nO IA  192.168.20.0\/24 [110\/20] via 10.1.12.2, 04:11:20, GigabitEthernet0\/0\n<\/code><\/pre>\n<p><strong>How to interpret the output:<\/strong><br \/>\n* <strong>Route Code (<code>O<\/code>, <code>O IA<\/code>, <code>O E1\/E2<\/code>, <code>O N1\/N2<\/code>):<\/strong> Shows whether the prefix was learned via intra-area (<code>O<\/code>), inter-area (<code>O IA<\/code>), standard external redistribution (<code>O E1<\/code>\/<code>O E2<\/code>), or NSSA redistribution (<code>O N1<\/code>\/<code>O N2<\/code>).<br \/>\n* <strong>Bracketed Values <code>[110\/11]<\/code>:<\/strong> The first number (<code>110<\/code>) is OSPF&#8217;s default Administrative Distance (AD). The second number (<code>11<\/code>) is the cumulative OSPF cost to reach the destination (<code>O E2<\/code> routes display only the external seed metric by default, without adding internal cost).<br \/>\n* <strong>Detailed Route Inspection:<\/strong> Run <code>show ip route 192.168.20.0<\/code> to view the exact originating Router ID, distance, metric, and last update timestamp for an individual prefix.<\/p>\n<p><strong>Key Takeaway:<\/strong> An LSA appearing in <code>show ip ospf database<\/code> only proves the advertisement was flooded; you must confirm it appears in <code>show ip route ospf<\/code> to guarantee the router is actually forwarding traffic over OSPF.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Troubleshooting_Missing_or_Stuck_OSPF_Neighbors_FAQ\"><\/span>Troubleshooting Missing or Stuck OSPF Neighbors (FAQ)<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>When your verification checks reveal missing peers, stuck adjacency states, or missing routes despite <code>FULL<\/code> neighbors, use these targeted diagnostic steps to isolate and fix the root cause.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Why_is_my_OSPF_neighbor_completely_missing_from_show_ip_ospf_neighbor\"><\/span>Why is my OSPF neighbor completely missing from <code>show ip ospf neighbor<\/code>?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If no neighbor entry appears at all, the router is either not receiving OSPF Hello packets on the interface or rejecting them immediately upon receipt. Check these common culprits in order:<br \/>\n1. <strong>Interface is Passive or Not in OSPF:<\/strong> Run <code>show ip protocols<\/code> and <code>show ip ospf interface brief<\/code>. If the interface is missing, the <code>network<\/code> statement wildcard mask does not match the interface IP, or <code>passive-interface<\/code> is suppressing Hellos.<br \/>\n2. <strong>Mismatched Hello\/Dead Timers or Area ID:<\/strong> Both peers must have identical Hello intervals, Dead intervals, Area IDs, and stub\/NSSA area flags. Run <code>show ip ospf interface &lt;interface&gt;<\/code> on both routers to compare.<br \/>\n3. <strong>Subnet Mask or Primary\/Secondary IP Mismatch:<\/strong> On broadcast and point-to-point links, neighbors must be on the same primary IP subnet.<br \/>\n4. <strong>Authentication Mismatch:<\/strong> Check <code>show ip ospf interface &lt;interface&gt;<\/code> to verify whether plain-text, MD5, or HMAC-SHA authentication keys and key-IDs match on both ends.<br \/>\n5. <strong>Multicast <code>224.0.0.5<\/code> Blocked:<\/strong> Ensure no ingress Access Control List (ACL), Control Plane Policing (CoPP) policy, or Layer 2 switch port filter is dropping OSPF multicast packets destined to <code>224.0.0.5<\/code>.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Why_is_an_OSPF_neighbor_stuck_in_the_INIT_state\"><\/span>Why is an OSPF neighbor stuck in the <code>INIT<\/code> state?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>As noted in the state comparison table above, <code>INIT<\/code> means the local router hears Hellos from the neighbor, but the neighbor does not list the local router&#8217;s RID in its outgoing Hellos (one-way communication).<br \/>\n* <strong>How to fix it:<\/strong> Check the remote neighbor first\u2014if the remote neighbor shows nothing in its <code>show ip ospf neighbor<\/code> table, an ACL, firewall, or broken transmit fiber is blocking packets traveling from the local router to the remote neighbor. Verify bidirectional Layer 2\/Layer 3 multicast forwarding with <code>ping 224.0.0.5<\/code> from both routers.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Why_is_an_OSPF_neighbor_stuck_in_EXSTART_or_EXCHANGE\"><\/span>Why is an OSPF neighbor stuck in <code>EXSTART<\/code> or <code>EXCHANGE<\/code>?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Getting stuck in <code>EXSTART<\/code> or <code>EXCHANGE<\/code> is almost always caused by an <strong>IP MTU mismatch<\/strong> between the two connected interfaces (for example, <code>1500<\/code> bytes on one router and <code>9000<\/code> jumbo frames or a reduced GRE\/IPsec tunnel MTU on the other). Because OSPF includes the interface IP MTU inside Database Description (DBD) packets, a neighbor rejects the DBD if the remote MTU is larger than its own.<br \/>\n* <strong>How to verify and fix it:<\/strong><br \/>\n  1. Run <code>show ip interface &lt;interface&gt; | include MTU<\/code> on both routers to compare exact IP MTU values.<br \/>\n  2. Set matching MTU values on both physical\/logical interfaces (recommended best practice).<br \/>\n  3. If you cannot modify the interface MTU immediately, apply <code>ip ospf mtu-ignore<\/code> under the interface configuration to bypass the DBD MTU check (ensure underlying Layer 2 links can still pass full-sized packets).<br \/>\n  4. If MTUs already match, verify that the two routers do not share a duplicate OSPF Router ID elsewhere in the network.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Why_do_neighbors_reach_FULL_state_but_OSPF_routes_are_missing_from_show_ip_route_ospf\"><\/span>Why do neighbors reach <code>FULL<\/code> state, but OSPF routes are missing from <code>show ip route ospf<\/code>?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If neighbors show <code>FULL<\/code> and LSAs exist in <code>show ip ospf database<\/code>, but routes fail to install in <code>show ip route ospf<\/code>, check the following:<br \/>\n* <strong>OSPF Network Type Mismatch:<\/strong> If one router is configured as <code>ip ospf network point-to-point<\/code> and the other is left at the default <code>ip ospf network broadcast<\/code>, both routers use the same <code>10\/40<\/code> timers and will form a <code>FULL<\/code> adjacency! However, the broadcast router expects a Type 2 Network LSA while the point-to-point router only uses Type 1 Router LSAs, causing the SPF tree calculation to fail. Verify with <code>show ip ospf interface &lt;interface&gt; | include Network Type<\/code>.<br \/>\n* <strong>Distribute-List or Lower Administrative Distance:<\/strong> A local <code>distribute-list in<\/code> under <code>router ospf<\/code> may be filtering the route from entering the RIB, or a static route (<code>AD 1<\/code>) \/ internal EIGRP route (<code>AD 90<\/code>) for the same exact prefix\/mask is winning over OSPF (<code>AD 110<\/code>).<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_I_safely_run_debug_ip_ospf_commands_on_a_production_router\"><\/span>How do I safely run <code>debug ip ospf<\/code> commands on a production router?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>When <code>show<\/code> commands aren&#8217;t enough, <code>debug ip ospf adj<\/code> and <code>debug ip ospf events<\/code> reveal real-time Hello mismatches, authentication failures, and DBD errors. To run them safely without overloading the router console:<\/p>\n<pre><code class=\"language-ios\">! 1. Verify CPU utilization is low before starting\nRouter# show processes cpu sorted | exclude 0.00%\n\n! 2. Ensure debug output goes to internal memory buffer (or SSH session), not slow serial console\nRouter# configure terminal\nRouter(config)# no logging console\nRouter(config)# logging buffered 65536 debugging\nRouter(config)# end\n\n! 3. Enable specific OSPF event or adjacency debugging\nRouter# debug ip ospf events\nRouter# debug ip ospf adj\n\n! 4. View captured logs in the buffer (or run 'terminal monitor' to stream to SSH)\nRouter# show logging | include OSPF\n\n! 5. Immediately disable all debugging once captured\nRouter# undebug all\n<\/code><\/pre>\n<p><strong>Key Takeaway:<\/strong> Match the symptom to the protocol phase\u2014missing neighbors point to Hello\/timer\/ACL issues, <code>EXSTART<\/code> points to MTU mismatches, and <code>FULL<\/code> adjacencies with missing routes point to OSPF network-type mismatches.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Cisco_Router_OSPF_Verification_and_Audit_CLI_Cheat_Sheet_Template\"><\/span>Cisco Router OSPF Verification and Audit CLI Cheat Sheet Template<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Copy and paste the command block below into a text file or terminal session during change windows and troubleshooting audits. Replace the bracketed placeholders (<code>&lt;PROCESS_ID&gt;<\/code>, <code>&lt;INTERFACE&gt;<\/code>, <code>&lt;VRF_NAME&gt;<\/code>) where filtering is needed, or run the standard commands directly.<\/p>\n<pre><code class=\"language-ios\">! =========================================================================\n! CISCO IOS \/ IOS XE OSPF VERIFICATION &amp; AUDIT CHEAT SHEET\n! =========================================================================\n! Prepare terminal for full, uninterrupted output capture\nterminal length 0\n\n! --- 1. GLOBAL PROCESS &amp; PROTOCOL AUDIT ---\nshow ip ospf\nshow ip protocols | section ospf\nshow running-config | section router ospf\nshow ip ospf border-routers\nshow ip ospf statistics detail\n\n! --- 2. INTERFACE STATUS &amp; TIMERS ---\nshow ip ospf interface brief\nshow ip ospf interface &lt;INTERFACE&gt;\nshow ip ospf interface | include line protocol|Internet Address|Network Type|Timer intervals|authentication\n\n! --- 3. NEIGHBOR ADJACENCY CHECKS ---\nshow ip ospf neighbor\nshow ip ospf neighbor detail\nshow ip ospf neighbor | exclude FULL|2WAY\/DROTHER\n\n! --- 4. LINK-STATE DATABASE (LSDB) INSPECTION ---\nshow ip ospf database\nshow ip ospf database database-summary\nshow ip ospf database self-originate\nshow ip ospf database max-age\nshow ip ospf database adv-router &lt;NEIGHBOR_ROUTER_ID&gt;\n\n! --- 5. ROUTING TABLE (RIB) &amp; CEF FORWARDING ---\nshow ip route ospf\nshow ip route &lt;DESTINATION_IP&gt; &lt;SUBNET_MASK&gt;\nshow ip cef &lt;DESTINATION_IP&gt; &lt;SUBNET_MASK&gt; detail\n\n! --- 6. VRF-AWARE OSPF VERIFICATION (IF USING MULTI-VRF) ---\nshow ip ospf vrf &lt;VRF_NAME&gt;\nshow ip ospf vrf &lt;VRF_NAME&gt; interface brief\nshow ip ospf vrf &lt;VRF_NAME&gt; neighbor\nshow ip route vrf &lt;VRF_NAME&gt; ospf\n\n! --- 7. TARGETED DIAGNOSTIC DEBUGS (USE WITH CAUTION) ---\nshow ip ospf events\ndebug ip ospf hello\ndebug ip ospf events\ndebug ip ospf adj\nundebug all\n\n! Restore default terminal pagination\nterminal length 24\n<\/code><\/pre>\n<p><strong>Key Takeaway:<\/strong> Keeping a standardized pre- and post-change CLI verification template allows you to capture baseline SPF statistics, neighbor counts, and route tables in seconds.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Cisco_IOS_OSPF_Command_Reference_and_Documentation_Specifications\"><\/span>Cisco IOS OSPF Command Reference and Documentation Specifications<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>This section provides the formal command syntax definitions, privilege mode requirements, software compatibility specifications, and official Cisco documentation pathways for OSPF verification commands.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Formal_Command_Syntax_and_Modes\"><\/span>Formal Command Syntax and Modes<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>All primary OSPF <code>show<\/code> verification commands operate in <strong>User EXEC (<code>&gt;<\/code>)<\/strong> or <strong>Privileged EXEC (<code>#<\/code>)<\/strong> mode, while configuration inspection (<code>show running-config<\/code>) and <code>debug<\/code> commands strictly require <strong>Privileged EXEC (<code>#<\/code>)<\/strong> mode.<\/p>\n<ul>\n<li><strong>Process Verification Syntax:<\/strong><br \/>\n  <code>show ip ospf [process-id]<\/code><\/li>\n<li><strong>Interface Verification Syntax:<\/strong><br \/>\n  <code>show ip ospf [process-id [area-id]] interface [type number] [brief]<\/code><\/li>\n<li><strong>Neighbor Verification Syntax:<\/strong><br \/>\n  <code>show ip ospf [process-id] [area-id] neighbor [type number] [neighbor-id] [detail]<\/code><\/li>\n<li><strong>Database Verification Syntax:<\/strong><br \/>\n  <code>show ip ospf [process-id [area-id]] database [router | network | summary | asbr-summary | external | nssa-external | opaque-link | opaque-area | opaque-as] [link-state-id] [adv-router ip-address | self-originate] [max-age]<\/code><\/li>\n<li><strong>Routing Table Verification Syntax:<\/strong><br \/>\n  <code>show ip route [vrf vrf-name] ospf [process-id]<\/code><\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"OS_Version_and_Platform_Compatibility_Matrix\"><\/span>OS Version and Platform Compatibility Matrix<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Operating System \/ Train<\/th>\n<th style=\"text-align: left;\">Process &amp; Neighbor Syntax<\/th>\n<th style=\"text-align: left;\">VRF-Aware OSPF Verification<\/th>\n<th style=\"text-align: left;\">OSPFv3 (IPv6 \/ Address Families)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>Cisco IOS (12.4T \/ 15.x)<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show ip ospf ...<\/code><\/td>\n<td style=\"text-align: left;\">Derived via <code>show ip ospf &lt;process-id&gt;<\/code> (where process is tied to VRF) or <code>show ip route vrf &lt;name&gt; ospf<\/code><\/td>\n<td style=\"text-align: left;\"><code>show ipv6 ospf neighbor<\/code>, <code>show ipv6 ospf interface brief<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Cisco IOS XE (16.x \/ 17.x)<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show ip ospf ...<\/code><\/td>\n<td style=\"text-align: left;\">Supports both <code>show ip ospf &lt;process-id&gt;<\/code> and <code>show ip ospf vrf &lt;vrf-name&gt; ...<\/code><\/td>\n<td style=\"text-align: left;\"><code>show ospfv3 neighbor<\/code>, <code>show ospfv3 vrf &lt;name&gt; interface brief<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Cisco IOS XR<\/strong> <em>(Reference Comparison)<\/em><\/td>\n<td style=\"text-align: left;\"><code>show ospf ...<\/code> (Omits <code>ip<\/code> keyword)<\/td>\n<td style=\"text-align: left;\"><code>show ospf vrf &lt;vrf-name&gt; neighbor<\/code><\/td>\n<td style=\"text-align: left;\"><code>show ospfv3 neighbor<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Cisco NX-OS<\/strong> <em>(Reference Comparison)<\/em><\/td>\n<td style=\"text-align: left;\"><code>show ip ospf ...<\/code><\/td>\n<td style=\"text-align: left;\"><code>show ip ospf neighbor vrf &lt;vrf-name&gt;<\/code><\/td>\n<td style=\"text-align: left;\"><code>show ipv6 ospf neighbor<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><span class=\"ez-toc-section\" id=\"Official_Cisco_Documentation_Portal_References\"><\/span>Official Cisco Documentation Portal References<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>For exhaustive field-by-field output descriptions, SNMP trap correlations, and release-specific command history tables on <code>cisco.com<\/code>, consult these official reference manuals:<br \/>\n1. <strong>Command Syntax and Output Field Descriptions:<\/strong><br \/>\n   <em>Document Title:<\/em> <strong>Cisco IOS IP Routing: OSPF Command Reference<\/strong><br \/>\n   <em>Navigation Path:<\/em> <code>Cisco Support<\/code> &gt; <code>Products<\/code> &gt; <code>Cisco IOS and NX-OS Software<\/code> &gt; <code>Cisco IOS Software<\/code> &gt; <code>Command References<\/code> &gt; <code>IP Routing: OSPF Command Reference<\/code> (Chapters: <em>OSPF Commands: show ip ospf through T<\/em> and <em>debug ip ospf<\/em>).<br \/>\n2. <strong>Configuration and Verification Guides by IOS XE Release:<\/strong><br \/>\n   <em>Document Title:<\/em> <strong>IP Routing: OSPF Configuration Guide, Cisco IOS XE [Release 17.x]<\/strong><br \/>\n   <em>Navigation Path:<\/em> <code>Cisco Support<\/code> &gt; <code>Switches \/ Routers<\/code> &gt; <code>[Platform Series, e.g., Catalyst 8000 or ISR 4000]<\/code> &gt; <code>Configuration Guides<\/code> &gt; <code>IP Routing: OSPF Configuration Guide<\/code> &gt; <code>Configuring OSPF<\/code> &gt; <code>Verifying OSPF Configuration<\/code>.<br \/>\n3. <strong>Troubleshooting TechNotes:<\/strong><br \/>\n   <em>Document Title:<\/em> <strong>Troubleshoot OSPF Neighbor Problems<\/strong> and <strong>Understand Open Shortest Path First (OSPF) &#8211; Design Guide<\/strong><br \/>\n   <em>Navigation Path:<\/em> <code>Cisco Support<\/code> &gt; <code>Technology Support<\/code> &gt; <code>IP<\/code> &gt; <code>IP Routing<\/code> &gt; <code>OSPF<\/code> &gt; <code>Troubleshooting TechNotes<\/code>.<\/p>\n<p><strong>Key Takeaway:<\/strong> Always verify whether your platform runs classic Cisco IOS\/IOS XE (<code>show ip ospf<\/code>) or OSPFv3 (<code>show ospfv3<\/code> \/ <code>show ipv6 ospf<\/code>) when consulting Cisco&#8217;s official command reference manuals.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span>Conclusion<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Checking OSPF status on a Cisco router is fastest and most reliable when you follow the protocol&#8217;s natural hierarchy. Start by verifying the local process and active interfaces with <code>show ip ospf<\/code> and <code>show ip ospf interface brief<\/code>, confirm that adjacent routers reach <code>FULL<\/code> (or expected <code>2WAY\/DROTHER<\/code>) states in <code>show ip ospf neighbor<\/code>, and validate that LSAs in <code>show ip ospf database<\/code> translate into active forwarding paths in <code>show ip route ospf<\/code>. By pairing these core verification commands with targeted MTU, timer, and network-type checks, you can quickly validate healthy routing domains and resolve adjacency issues with confidence.<\/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-ospf-status-on-cisco-router_24594.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+OSPF+Status+on+Cisco+Router+https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.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-ospf-status-on-cisco-router_24594.html\",\"How to Check OSPF Status on 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>Verifying Open Shortest Path First (OSPF) operational health on a Cisco router requires more than checking whether a neighbor appears in a list. Because OSPF is a link-state routing protocol, a healthy deployment depends on four distinct layers working together: an active local OSPF process, properly bound interfaces, synchronized neighbor adjacencies, and a consistent Link-State&#8230; &raquo; <a class=\"read-more-link\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.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 OSPF Status on 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-ospf-status-on-cisco-router_24594.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 OSPF Status on Cisco Router - SPOTO Official Blog\" \/>\n<meta property=\"og:description\" content=\"Verifying Open Shortest Path First (OSPF) operational health on a Cisco router requires more than checking whether a neighbor appears in a list. Because OSPF is a link-state routing protocol, a healthy deployment depends on four distinct layers working together: an active local OSPF process, properly bound interfaces, synchronized neighbor adjacencies, and a consistent Link-State... &raquo; read more\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\" \/>\n<meta property=\"og:site_name\" content=\"SPOTO Official Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-17T09:10:14+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=\"19 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-ospf-status-on-cisco-router_24594.html#webpage\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\",\"name\":\"How to Check OSPF Status on Cisco Router - SPOTO Official Blog\",\"isPartOf\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#website\"},\"datePublished\":\"2026-11-17T09:10:14+00:00\",\"dateModified\":\"2026-11-17T09:10:14+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/cciedump.spoto.net\/blog\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Check OSPF Status on Cisco Router\"}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html#article\",\"isPartOf\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html#webpage\"},\"author\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1\"},\"headline\":\"How to Check OSPF Status on Cisco Router\",\"datePublished\":\"2026-11-17T09:10:14+00:00\",\"dateModified\":\"2026-11-17T09:10:14+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html#webpage\"},\"wordCount\":2525,\"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-ospf-status-on-cisco-router_24594.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 OSPF Status on 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-ospf-status-on-cisco-router_24594.html","og_locale":"en_US","og_type":"article","og_title":"How to Check OSPF Status on Cisco Router - SPOTO Official Blog","og_description":"Verifying Open Shortest Path First (OSPF) operational health on a Cisco router requires more than checking whether a neighbor appears in a list. Because OSPF is a link-state routing protocol, a healthy deployment depends on four distinct layers working together: an active local OSPF process, properly bound interfaces, synchronized neighbor adjacencies, and a consistent Link-State... &raquo; read more","og_url":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html","og_site_name":"SPOTO Official Blog","article_published_time":"2026-11-17T09:10:14+00:00","twitter_card":"summary_large_image","twitter_misc":{"Written by":"SPOTO \u7f16\u8f91","Est. reading time":"19 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-ospf-status-on-cisco-router_24594.html#webpage","url":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html","name":"How to Check OSPF Status on Cisco Router - SPOTO Official Blog","isPartOf":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#website"},"datePublished":"2026-11-17T09:10:14+00:00","dateModified":"2026-11-17T09:10:14+00:00","breadcrumb":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cciedump.spoto.net\/blog"},{"@type":"ListItem","position":2,"name":"How to Check OSPF Status on Cisco Router"}]},{"@type":"Article","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html#article","isPartOf":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html#webpage"},"author":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1"},"headline":"How to Check OSPF Status on Cisco Router","datePublished":"2026-11-17T09:10:14+00:00","dateModified":"2026-11-17T09:10:14+00:00","mainEntityOfPage":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-ospf-status-on-cisco-router_24594.html#webpage"},"wordCount":2525,"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-ospf-status-on-cisco-router_24594.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\/24594"}],"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=24594"}],"version-history":[{"count":0,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/posts\/24594\/revisions"}],"wp:attachment":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/media?parent=24594"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/categories?post=24594"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/tags?post=24594"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}